CVE-2026-72306: Linux kernel · vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d8715b5a8fdb23fef576700e71d0c253dbeddad4 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d8715b5a8fdb23fef576700e71d0c253dbeddad4, d7e7c813834c6c05c26033456ab7169e2f9c99eb, c83ad3dfa6d9953d5ce6839416bf5a1bfc50285a +4
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter There is one race case in vduse_dev_msg_sync and vduse_dev_read_iter: vduse_dev_read_iter(): lock(msg_lock); dequeue_msg(send_list); unlock(msg_lock); vduse_dev_msg_sync(): wait_timeout() finish lock(msg_lock); check msg->complete is false list_del(msg); <- double list_del() crash! To fix this case, we shall ensure vduse_msg is on send_list or recv_list outside the msg_lock critical section.
References
- git.kernel.org/stable/c/c83ad3dfa6d9953d5ce6839416bf5a1bfc50285a (opens in a new tab)
- git.kernel.org/stable/c/09723f26ed801c083e914cec4cc0e1af4b933dc7 (opens in a new tab)
- git.kernel.org/stable/c/d7e7c813834c6c05c26033456ab7169e2f9c99eb (opens in a new tab)
- git.kernel.org/stable/c/3755965adbb617f4283ac6ccd351ed0676843cba (opens in a new tab)
- git.kernel.org/stable/c/d8715b5a8fdb23fef576700e71d0c253dbeddad4 (opens in a new tab)
- git.kernel.org/stable/c/8062ff9d366c4bc4ae775e14eac9a769f20c60dd (opens in a new tab)
- git.kernel.org/stable/c/ae9c13b6fd79087cc5a216ee1649b6f012c2a238 (opens in a new tab)