LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48786: vsock: remove vsock from connected table when connect is interrupted by a signal

In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal vsock_connect() expects that the socket could already be in the TCP_ESTABLISHED state when the connecting task wakes up with a signal pending. If this happens the socket will be in the connected table, and it is not removed when the socket state is reset. In this situation it's common for the process to retry connect(), and if the connection is successful the socket will be added to the connected table a second time, corrupting the list. Prevent this by calling vsock_remove_connected() if a signal is received while waiting for a connection. This is harmless if the socket is not in the connected table, and if it is in the table then removing it will prevent list corruption from a double add. Note for backporting: this patch requires d5afa82c977e ("vsock: correct removal of socket from the list"), which is in all current stable trees except 4.9.y.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw affects vsock, a communication mechanism commonly used between hosts and virtual machines. If a connection attempt is interrupted at a specific point, the kernel can leave stale state and later corrupt an internal list. The public sources do not state confirmed exploitation or a business impact category.

Executive priority

Treat this as a patch-management item for Linux virtualization environments. Escalate priority where vsock is used heavily, but do not classify it as emergency without vendor severity, impact, or exploitation evidence.

Technical view

In vsock_connect(), a socket can enter TCP_ESTABLISHED and be placed in the connected table before the waiting task wakes with a pending signal. The old path reset socket state without removing it from the connected table. A retry could add the same socket again, corrupting the list. The fix removes the socket on interrupted connect.

Likely exposure

Exposure is most relevant on Linux systems using AF_VSOCK or virtualization features that rely on vsock. The bundle lists Linux kernel versions and stable-line fixes, but does not provide distribution package names or product-specific advisories.

Exploitation context

No active exploitation is indicated in the provided sources, and KEV is false. The source describes a race/state-handling bug triggered by an interrupted connection attempt, but does not provide exploitability, privileges required, or demonstrated impact.

Researcher notes

The key condition is interrupted vsock_connect() after the socket reaches TCP_ESTABLISHED and enters the connected table. The patch notes a backport dependency on d5afa82c977e for correct socket list removal, with 4.9.y called out as an exception at the time of the note.

Mitigation direction

  • Upgrade Linux kernels to vendor builds containing the referenced stable fixes.
  • Check distribution advisories for package-specific fixed kernel versions.
  • Prioritize systems using virtualization or vsock-dependent workloads.
  • If upgrade timing is constrained, review vendor guidance for temporary exposure reduction.

Validation and detection

  • Inventory Linux kernel versions across virtualized and host environments.
  • Check whether AF_VSOCK or vsock-related modules are present and in use.
  • Map each kernel to the applicable stable fix reference or vendor advisory.
  • Confirm patched systems include the vsock_remove_connected() interruption fix.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48786 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238, d021c344051af91f42c5ba9fdedc176740cbd238unaffected
LinuxLinux3.9, 0, 4.9.303, 4.14.268, 4.19.231, 5.4.181, 5.10.102, 5.15.25, 5.16.11, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.