CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers
Noroxi assessment
Priority: Monitor (action score 31/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa, 1b4a3c2f0509e7b0e65667f3c36676a849ee2755, 3a07249981629ace483ebbef81ef6b34c2d2afec.
Low priority for now. Upgrade to Linux Linux 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa, 1b4a3c2f0509e7b0e65667f3c36676a849ee2755, 3a07249981629ace483ebbef81ef6b34c2d2afec 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: 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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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
- 7.8
- 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
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before f398b7d92cd999191249830b9171c9bd787a9a91affected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before 1b4a3c2f0509e7b0e65667f3c36676a849ee2755affected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before cfe107b02a3c3f049e0dc15b6a36625f048eda2aaffected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before 90d35d2b8e47afd68fe2a4dd0eeb60bc71641775affected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before e01071ea006c9b952125ed8b0cc90ac7bd356cceaffected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before 7099e7148f81c605bbc319b16ce0131540341560affected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aaaffected · git
- 8a39d00670f0792c1186e442e1dd28fe0326f2ee and later · before 3a07249981629ace483ebbef81ef6b34c2d2afecaffected · 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72276Aug 15, 2026 · fbdev: metronomefb: fix potential memory leak in metronomefb_probe()0Monitor
- ← EarlierCVE-2026-72280Aug 15, 2026 · KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL228Monitor
- Later →CVE-2026-72284Aug 15, 2026 · KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs28Monitor
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 | 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa | Vendor (CNA) |
| Linux Linux | 1b4a3c2f0509e7b0e65667f3c36676a849ee2755 | Vendor (CNA) |
| Linux Linux | 3a07249981629ace483ebbef81ef6b34c2d2afec | Vendor (CNA) |
| Linux Linux | 7099e7148f81c605bbc319b16ce0131540341560 | Vendor (CNA) |
| Linux Linux | 90d35d2b8e47afd68fe2a4dd0eeb60bc71641775 | Vendor (CNA) |
| Linux Linux | cfe107b02a3c3f049e0dc15b6a36625f048eda2a | Vendor (CNA) |
| Linux Linux | e01071ea006c9b952125ed8b0cc90ac7bd356cce | Vendor (CNA) |
| Linux Linux | f398b7d92cd999191249830b9171c9bd787a9a91 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | 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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Low
- 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:L/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/1b4a3c2f0509e7b0e65667f3c36676a849ee2755
- git.kernel.org/stable/c/3a07249981629ace483ebbef81ef6b34c2d2afec
- git.kernel.org/stable/c/7099e7148f81c605bbc319b16ce0131540341560
- git.kernel.org/stable/c/90d35d2b8e47afd68fe2a4dd0eeb60bc71641775
- git.kernel.org/stable/c/cfe107b02a3c3f049e0dc15b6a36625f048eda2a
- git.kernel.org/stable/c/e01071ea006c9b952125ed8b0cc90ac7bd356cce
- git.kernel.org/stable/c/f398b7d92cd999191249830b9171c9bd787a9a91
Vendor advisories and official records. Exploit/PoC links are deliberately left out.