vsock/virtio: flush works in dependency order
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 165a330a68b5f299d8735f0194c314cb2e571269, 2187a56f2fd1715d54daed6392809223c60544f3, 531e2ac2dab1ab90a16427c4f9c86663633e9487.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 165a330a68b5f299d8735f0194c314cb2e571269, 2187a56f2fd1715d54daed6392809223c60544f3, 531e2ac2dab1ab90a16427c4f9c86663633e9487 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.8affected
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before e059a14c1067bcc4f7b1947cd09f2baab98e340faffected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before 531e2ac2dab1ab90a16427c4f9c86663633e9487affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before f3313d952fc380cff53db9a28451a8807aa67b43affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before 2187a56f2fd1715d54daed6392809223c60544f3affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before 165a330a68b5f299d8735f0194c314cb2e571269affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before da5e9f08714c19ba04e6863aca69d40f042f2e04affected · git
- 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and later · before 728836ebca239810f164262b10211ef59182f811affected · git
- before 4.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.6-1.1 | 7.2.6-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80930Sep 11, 2026 · tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout0Monitor
- ← EarlierCVE-2026-80931Sep 11, 2026 · w1: ds28e17: reject an oversize length on an I2C block read31Monitor
- Later →CVE-2026-80933Sep 11, 2026 · wifi: mt76: mt7996: validate default EEPROM firmware size31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 165a330a68b5f299d8735f0194c314cb2e571269 | Vendor (CNA) |
| Linux Linux | 2187a56f2fd1715d54daed6392809223c60544f3 | Vendor (CNA) |
| Linux Linux | 531e2ac2dab1ab90a16427c4f9c86663633e9487 | Vendor (CNA) |
| Linux Linux | 728836ebca239810f164262b10211ef59182f811 | Vendor (CNA) |
| Linux Linux | b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94 | Vendor (CNA) |
| Linux Linux | da5e9f08714c19ba04e6863aca69d40f042f2e04 | Vendor (CNA) |
| Linux Linux | e059a14c1067bcc4f7b1947cd09f2baab98e340f | Vendor (CNA) |
| Linux Linux | f3313d952fc380cff53db9a28451a8807aa67b43 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2187a56f2fd1715d54daed6392809223c60544f3
- git.kernel.org/stable/c/531e2ac2dab1ab90a16427c4f9c86663633e9487
- git.kernel.org/stable/c/728836ebca239810f164262b10211ef59182f811
- git.kernel.org/stable/c/b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94
- git.kernel.org/stable/c/da5e9f08714c19ba04e6863aca69d40f042f2e04
- git.kernel.org/stable/c/e059a14c1067bcc4f7b1947cd09f2baab98e340f
- git.kernel.org/stable/c/f3313d952fc380cff53db9a28451a8807aa67b43
Vendor advisories and official records. Exploit/PoC links are deliberately left out.