Linux Kernel up to 7.2-rc3 KVM kvm_io_bus_get_dev locking

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$0-$5k0.50-

Summaryinfo

A vulnerability categorized as very critical has been discovered in Linux Kernel up to 7.2-rc3. The affected element is the function kvm_io_bus_get_dev of the component KVM. Executing a manipulation can lead to locking. This vulnerability appears as CVE-2026-72282. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.2-rc3 and classified as very critical. This vulnerability affects the function kvm_io_bus_get_dev of the component KVM. The manipulation with an unknown input leads to a locking vulnerability. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-72282 since 08/09/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc4 eliminates this vulnerability. Applying the patch f398b7d92cd999191249830b9171c9bd787a9a91/1b4a3c2f0509e7b0e65667f3c36676a849ee2755/cfe107b02a3c3f049e0dc15b6a36625f048eda2a/90d35d2b8e47afd68fe2a4dd0eeb60bc71641775/e01071ea006c9b952125ed8b0cc90ac7bd356cce/7099e7148f81c605bbc319b16ce0131540341560/0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa/3a07249981629ace483ebbef81ef6b34c2d2afec is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Locking
CWE: CWE-667
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc4
Patch: f398b7d92cd999191249830b9171c9bd787a9a91/1b4a3c2f0509e7b0e65667f3c36676a849ee2755/cfe107b02a3c3f049e0dc15b6a36625f048eda2a/90d35d2b8e47afd68fe2a4dd0eeb60bc71641775/e01071ea006c9b952125ed8b0cc90ac7bd356cce/7099e7148f81c605bbc319b16ce0131540341560/0cbae0e296d27ce4c4cce83e34d40c2bfd8133aa/3a07249981629ace483ebbef81ef6b34c2d2afec

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72282 (🔒)
GCVE (CVE): GCVE-0-2026-72282
GCVE (VulDB): GCVE-100-390748

Entryinfo

Created: 08/15/2026 14:42
Changes: 08/15/2026 14:42 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!