Skip to main content
VulnerabilityPublished Updated

CVE-2026-46214: Linux kernel · vsock/virtio: fix accept queue count leak on transport mismatch

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd51e810affa38d735d04261e673b2a5fe9c8665 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in fd51e810affa38d735d04261e673b2a5fe9c8665, f66c7904fb6f0e420a654bc90909e64a25d00896, e9edf9893cf26d060705c910a9b62d8cc96ed56a +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < fd51e810affa38d735d04261e673b2a5fe9c8665
Fixed in
  • fd51e810affa38d735d04261e673b2a5fe9c8665
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < f66c7904fb6f0e420a654bc90909e64a25d00896
Fixed in
  • f66c7904fb6f0e420a654bc90909e64a25d00896
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < e9edf9893cf26d060705c910a9b62d8cc96ed56a
Fixed in
  • e9edf9893cf26d060705c910a9b62d8cc96ed56a
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 29371f3cc83e2a92265b4768014a30b80234112f
Fixed in
  • 29371f3cc83e2a92265b4768014a30b80234112f
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 65c484726e74013a2ec7ba67a34d87760ae8f390
Fixed in
  • 65c484726e74013a2ec7ba67a34d87760ae8f390
LinuxLinuxAffected
  • ≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, < 52bcb57a4e8a0865a76c587c2451906342ae1b2d
Fixed in
  • 52bcb57a4e8a0865a76c587c2451906342ae1b2d

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix accept queue count leak on transport mismatch virtio_transport_recv_listen() calls sk_acceptq_added() before vsock_assign_transport(). If vsock_assign_transport() fails or selects a different transport, the error path returns without calling sk_acceptq_removed(), permanently incrementing sk_ack_backlog. After approximately backlog+1 such failures, sk_acceptq_is_full() returns true, causing the listener to reject all new connections. Fix by moving sk_acceptq_added() to after the transport validation, matching the pattern used by vmci_transport and hyperv_transport.

References

Community reviews

Loading reviews…