CVE-2021-47060

KVM: Stop looking for coalesced MMIO zones if the bus is destroyed

HIGH
7.8
CVSS Score
Published: February 29, 2024 at 10:37 PM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: Stop looking for coalesced MMIO zones if the bus is destroyed Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev() fails to allocate memory for the new instance of the bus. If it can't instantiate a new bus, unregister_dev() destroys all devices _except_ the target device. But, it doesn't tell the caller that it obliterated the bus and invoked the destructor for all devices that were on the bus. In the coalesced MMIO case, this can result in a deleted list entry dereference due to attempting to continue iterating on coalesced_zones after future entries (in the walk) have been deleted. Opportunistically add curly braces to the for-loop, which encompasses many lines but sneaks by without braces due to the guts being a single if statement.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.200v ≥ 4.19.148v ≥ 4.4.238v ≥ 4.9.238v ≥ 5.8.104.14.200 ≤ v < 4.154.19.148 ≤ v < 4.204.4.238 ≤ v < 4.54.9.238 ≤ v < 4.105.11 ≤ v < 5.11.215.12 ≤ v < 5.12.45.4.66 ≤ v < 5.4.1195.8.10 ≤ v < 5.95.9 ≤ v < 5.10.375.9 ≤ v < 5.11.215.9 ≤ v < 5.12.45.9 ≤ v < 5.1319184bd06f488af62924ff1747614a8cb284ad634.14.2004.19.1484.4.2384.9.23840a023f681befd9b2862a3c16fb306a38b359ae541b2ea7a6a11e2b1a7f2c29e1675a709a6b2b98d5.4.665.8.105.968c125324b5e1d1d22805653735442923d896a1d840e124f89a5127e7eb97ebf377f4b8ca745c070f0dfffce3f4ffd5f822568a4a6fb34c010e939d1f65886606c2d3b562716de030706dfe1bea4ed5e
Vendor states this is fixed in 168e82f640ed1891a700bdb43e37da354b2ab63c (fixed)
Vendor states this is fixed in 2a20592baff59c5351c5200ec667e1a2aa22af85 (fixed)
Vendor states this is fixed in 50cbad42bfea8c052b7ca590bd4126cdc898713c (fixed)
Vendor states this is fixed in 5d3c4c79384af06e3c8e25b7770b6247496b4417 (fixed)
Vendor states this is fixed in 7d1bc32d6477ff96a32695ea4be8144e4513ab2d (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.37 (unaffected)
Vendor states this is fixed in 5.11.21 (unaffected)
Vendor states this is fixed in 5.12.4 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.4.119 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/168e82f640ed1891a700bdb43e37da354b2ab63c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2a20592baff59c5351c5200ec667e1a2aa22af85
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/50cbad42bfea8c052b7ca590bd4126cdc898713c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5d3c4c79384af06e3c8e25b7770b6247496b4417
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7d1bc32d6477ff96a32695ea4be8144e4513ab2d

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card