CVE-2026-72282

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers

kvm_io_bus_get_dev() returns a device that is only matched by the address, and nothing else. This can cause a lifetime issue if the matched device is not the expected type, as by the time the caller can introspect the object, it might be gone (the srcu lock having been dropped).

Given that there is only a single user of this helper, the simplest option is to move the locking responsibility to the caller, which can keep the srcu lock held for as long as it wants.

Note that this aligns with other kvm_io_bus*() helpers, which already require the srcu lock to be held by the callers.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f398b7d92cd999191249830b9171c9bd787a9a91
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e01071ea006c9b952125ed8b0cc90ac7bd356cce
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cfe107b02a3c3f049e0dc15b6a36625f048eda2a
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90d35d2b8e47afd68fe2a4dd0eeb60bc71641775
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7099e7148f81c605bbc319b16ce0131540341560
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a07249981629ace483ebbef81ef6b34c2d2afec
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b4a3c2f0509e7b0e65667f3c36676a849ee2755
generic

KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa

Vendor Advisories for CVE-2026-72282(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:57 UTCGHSA enrichment
  3. 2026-08-20 08:37 UTCGHSA enrichment
  4. 2026-08-19 20:18 UTCEG score recompute
  5. 2026-08-19 20:18 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:58 UTCGHSA enrichment
  8. 2026-08-18 19:39 UTCEG score recompute
  9. 2026-08-18 19:39 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:19 UTCGHSA enrichment
  13. 2026-08-17 19:00 UTCEG score recompute
  14. 2026-08-17 19:00 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:20 UTCEG score recompute
  17. 2026-08-17 06:20 UTCGHSA enrichment
  18. 2026-08-17 05:59 UTCEG score recompute▲ 7.80
  19. 2026-08-17 05:59 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-08-17 05:31 UTCEG score recompute
  22. 2026-08-17 05:31 UTCGHSA enrichment
  23. 2026-08-17 05:25 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 5 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 06:38 UTCGHSA enrichment
  3. 2026-08-15 06:23 UTCNVD update
  4. 2026-08-15 06:08 UTCEG score recompute
  5. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72282?
CVE-2026-72282 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: Move kvmiobusgetdev() locking responsibilities to callers kvmiobusgetdev() returns a device that is only matched by the address, and nothing else. This can cause a lifetime issue if the matched device is not the expected type,…
When was CVE-2026-72282 disclosed?
CVE-2026-72282 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72282 actively exploited?
CVE-2026-72282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72282?
CVE-2026-72282 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72282?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72282, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72282

Explore →

Is Your Infrastructure Affected by CVE-2026-72282?

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

Start Free Scan →Browse All CVEs