# vsock/virtio: fix accept queue count leak on transport mismatch

CVE record · `CVE-2026-46214`

- **Identifiers:** `CVE-2026-46214`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 28 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 28 May 2026, 09:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before 2ea5d2c79edcc99c7dbe0bb7518f5e1ee2a2391f` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before fd51e810affa38d735d04261e673b2a5fe9c8665` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before f66c7904fb6f0e420a654bc90909e64a25d00896` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before 65c484726e74013a2ec7ba67a34d87760ae8f390` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before 29371f3cc83e2a92265b4768014a30b80234112f` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before e9edf9893cf26d060705c910a9b62d8cc96ed56a` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before 6d3275fc4ed968938e1d556c344798046776668d` (git)
  - affected: `c0cfa2d8a788fcf45df5bf4070ab2474c88d543a to before 52bcb57a4e8a0865a76c587c2451906342ae1b2d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.5`
  - unaffected: `before 5.5` (semver)
  - unaffected: `5.10.258 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.175 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.140 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.90 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.32 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.9 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 28 May 2026, 09:40 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46214)
- 28 May 2026, 10:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46214)

## Sources

- [CVE List: CVE-2026-46214](https://www.cve.org/CVERecord?id=CVE-2026-46214)
- [NVD: CVE-2026-46214](https://nvd.nist.gov/vuln/detail/CVE-2026-46214)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-46214>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-46214/>. Everything for agents: <https://agentprime.io/llms.txt>.
