Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-80932

vsock/virtio: flush works in dependency order

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

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. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in e059a14c1067bcc4f7b1947cd09f2baab98e340f; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in 531e2ac2dab1ab90a16427c4f9c86663633e9487; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in f3313d952fc380cff53db9a28451a8807aa67b43; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in 2187a56f2fd1715d54daed6392809223c60544f3; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in 165a330a68b5f299d8735f0194c314cb2e571269; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in da5e9f08714c19ba04e6863aca69d40f042f2e04; From 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 · fixed in 728836ebca239810f164262b10211ef59182f811

  • Linux Linux

    4.8

  • KernelLinux

    From 4.8.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4

References 8

git.kernel.org