Answer in brief
CVE-2026-72282 records a Unknown severity vulnerability in KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72282 records a Unknown severity vulnerability in KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <f398b7d92cd999191249830b9171c9bd787a9a91 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <1b4a3c2f0509e7b0e65667f3c36676a849ee2755 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <cfe107b02a3c3f049e0dc15b6a36625f048eda2a || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <90d35d2b8e47afd68fe2a4dd0eeb60bc71641775 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <e01071ea006c9b952125ed8b0cc90ac7bd356cce || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <7099e7148f81c605bbc319b16ce0131540341560 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <3a07249981629ace483ebbef81ef6b34c2d2afec | f398b7d92cd999191249830b9171c9bd787a9a91, 1b4a3c2f0509e7b0e65667f3c36676a849ee2755, cfe107b02a3c3f049e0dc15b6a36625f048eda2a, 90d35d2b8e47afd68fe2a4dd0eeb60bc71641775, e01071ea006c9b952125ed8b0cc90ac7bd356cce, 7099e7148f81c605bbc319b16ce0131540341560, 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa, 3a07249981629ace483ebbef81ef6b34c2d2afec |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <f398b7d92cd999191249830b9171c9bd787a9a91 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <1b4a3c2f0509e7b0e65667f3c36676a849ee2755 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <cfe107b02a3c3f049e0dc15b6a36625f048eda2a || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <90d35d2b8e47afd68fe2a4dd0eeb60bc71641775 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <e01071ea006c9b952125ed8b0cc90ac7bd356cce || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <7099e7148f81c605bbc319b16ce0131540341560 || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa || >=8a39d00670f0792c1186e442e1dd28fe0326f2ee <3a07249981629ace483ebbef81ef6b34c2d2afec | f398b7d92cd999191249830b9171c9bd787a9a91, 1b4a3c2f0509e7b0e65667f3c36676a849ee2755, cfe107b02a3c3f049e0dc15b6a36625f048eda2a, 90d35d2b8e47afd68fe2a4dd0eeb60bc71641775, e01071ea006c9b952125ed8b0cc90ac7bd356cce, 7099e7148f81c605bbc319b16ce0131540341560, 0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa, 3a07249981629ace483ebbef81ef6b34c2d2afec |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.