CVE-2026-72306

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-72306(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 83 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-18 03:16 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-12 15:42 UTCEG score recompute
  11. 2026-10-11 19:27 UTCEG score recompute
  12. 2026-10-11 16:43 UTCEG score recompute
  13. 2026-10-11 14:03 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-04 04:08 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-30 21:10 UTCEG score recompute
  25. 2026-09-30 21:10 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
Show 54 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-09-27 08:41 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-09-22 20:49 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  8. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-09-19 11:07 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-09-16 01:59 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  15. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-09-12 19:09 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  17. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-09-09 12:20 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  21. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-09-06 05:29 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  24. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-02 22:40 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  26. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-08-30 09:39 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  31. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-08-27 02:47 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  34. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-08-23 19:58 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  37. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  38. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  39. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  40. 2026-08-20 13:09 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  41. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  42. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  44. 2026-08-17 06:19 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  45. 2026-08-17 06:18 UTCNVD update
  46. 2026-08-17 05:30 UTCEG score recompute
  47. 2026-08-17 05:30 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  48. 2026-08-17 05:25 UTCMITRE cvelistV5
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-08-15 06:37 UTCGHSA enrichmentGHSA-p7f7-389q-3p34
  52. 2026-08-15 06:23 UTCNVD update
  53. 2026-08-15 06:07 UTCEG score recompute
  54. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-72306?
CVE-2026-72306 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: vduse: Fix race in vdusedevmsgsync and vdusedevreaditer There is one race case in vdusedevmsgsync and vdusedevreaditer: vdusedevread_iter(): lock(msg_lock); dequeuemsg(sendlist); unlock(msg_lock); vdusedevmsg_sync(): wait_timeout()…
When was the CVE record for CVE-2026-72306 published?
The CVE record for CVE-2026-72306 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-72306 actively exploited?
CVE-2026-72306 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-72306?
A fix for CVE-2026-72306 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72306 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72306

Explore →

Is Your Infrastructure Affected by CVE-2026-72306?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.