CVE-2021-47061

KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU

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: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU If allocating a new instance of an I/O bus fails when unregistering a device, wait to destroy the device until after all readers are guaranteed to see the new null bus. Destroying devices before the bus is nullified could lead to use-after-free since readers expect the devices on their reference of the bus to remain valid.

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.4.66v ≥ 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.55.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 03c6cccedd3913006744faa252a4da5145299343 (fixed)
Vendor states this is fixed in 2ee3757424be7c1cd1d0bbfa6db29a7edd82a250 (fixed)
Vendor states this is fixed in 30f46c6993731efb2a690c9197c0fd9ed425da2d (fixed)
Vendor states this is fixed in 4e899ca848636b37e9ac124bc1723862a7d7d927 (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)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.9 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/03c6cccedd3913006744faa252a4da5145299343
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2ee3757424be7c1cd1d0bbfa6db29a7edd82a250
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/30f46c6993731efb2a690c9197c0fd9ed425da2d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4e899ca848636b37e9ac124bc1723862a7d7d927

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
CWE-416

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