Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46214, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < 2ea5d2c79edcc99c7dbe0bb7518f5e1ee2a2391f
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < fd51e810affa38d735d04261e673b2a5fe9c8665
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < f66c7904fb6f0e420a654bc90909e64a25d00896
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < 65c484726e74013a2ec7ba67a34d87760ae8f390
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < 29371f3cc83e2a92265b4768014a30b80234112f
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < e9edf9893cf26d060705c910a9b62d8cc96ed56a
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < 6d3275fc4ed968938e1d556c344798046776668d
    • affected c0cfa2d8a788fcf45df5bf4070ab2474c88d543a – < 52bcb57a4e8a0865a76c587c2451906342ae1b2d
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.90 – ≤ 6.12.*
    • unaffected 6.18.32 – ≤ 6.18.*
    • unaffected 7.0.9 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46214 badge
[![CVE-2026-46214](https://cveledger.app/badge/CVE-2026-46214.svg)](https://cveledger.app/cve/CVE-2026-46214)

Record last updated .