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-80932vsock/virtio: flush works in dependency order

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: flush works in dependency order virtio_vsock_remove() stops the virtqueues and then flushes each work item before freeing the enclosing virtio_vsock. The current order does not account for dependencies between those items: tx_work may queue send_pkt_work, and send_pkt_work may queue rx_work. In particular, send_pkt_work can set restart_rx and release tx_lock. The remove path can then stop the queues and flush rx_work before send_pkt_work queues it. Although the later send_pkt_work flush waits for that producer to finish, nothing waits for the newly queued rx_work, so kfree(vsock) can race with it. KASAN reported: BUG: KASAN: slab-use-after-free in virtio_transport_rx_work+0x487/0x4b0 Read of size 8 at addr ffff888114c2b008 by task kworker/1:1/47 Workqueue: virtio_vsock virtio_transport_rx_work Call Trace: virtio_transport_rx_work+0x487/0x4b0 process_one_work+0x688/0x1120 worker_thread+0x45b/0xd10 Allocated by task 1: virtio_vsock_probe+0xef/0x6b0 Freed by task 84: kfree+0x131/0x3c0 virtio_vsock_remove+0xd1/0x100 Flush the works in producer-to-consumer order. virtio_vsock_vqs_del() has already disabled the queue callbacks and cleared the run flags, so after tx_work and send_pkt_work are drained, no source remains that can queue rx_work after its flush.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 days 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-80932, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < e059a14c1067bcc4f7b1947cd09f2baab98e340f
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < 531e2ac2dab1ab90a16427c4f9c86663633e9487
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < f3313d952fc380cff53db9a28451a8807aa67b43
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < 2187a56f2fd1715d54daed6392809223c60544f3
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < 165a330a68b5f299d8735f0194c314cb2e571269
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < da5e9f08714c19ba04e6863aca69d40f042f2e04
    • affected 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 – < 728836ebca239810f164262b10211ef59182f811
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .