CVE-2021-47061: KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
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.24% (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 03c6cccedd3913006744faa252a4da5145299343, 2ee3757424be7c1cd1d0bbfa6db29a7edd82a250, 30f46c6993731efb2a690c9197c0fd9ed425da2d.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 03c6cccedd3913006744faa252a4da5145299343, 2ee3757424be7c1cd1d0bbfa6db29a7edd82a250, 30f46c6993731efb2a690c9197c0fd9ed425da2d 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: 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.
- Published
- Feb 29, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- f0dfffce3f4ffd5f822568a4a6fb34c010e939d1, 840e124f89a5127e7eb97ebf377f4b8ca745c070, 40a023f681befd9b2862a3c16fb306a38b359ae5, 19184bd06f488af62924ff1747614a8cb284ad63, 41b2ea7a6a11e2b1a7f2c29e1675a709a6b2b98d, 68c125324b5e1d1d22805653735442923d896a1d, 5.9affected
- f65886606c2d3b562716de030706dfe1bea4ed5e and later · before 03c6cccedd3913006744faa252a4da5145299343affected · git
- f65886606c2d3b562716de030706dfe1bea4ed5e and later · before 4e899ca848636b37e9ac124bc1723862a7d7d927affected · git
- f65886606c2d3b562716de030706dfe1bea4ed5e and later · before 30f46c6993731efb2a690c9197c0fd9ed425da2daffected · git
- f65886606c2d3b562716de030706dfe1bea4ed5e and later · before 2ee3757424be7c1cd1d0bbfa6db29a7edd82a250affected · git
- 4.4.238 and later · before 4.5affected · semver
- 4.9.238 and later · before 4.10affected · semver
- 4.14.200 and later · before 4.15affected · semver
- 4.19.148 and later · before 4.20affected · semver
- 5.4.66 and later · before 5.5affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.9 and later · before 5.10.37
- linux linux kernel5.11 and later · before 5.11.21
- linux linux kernel5.12 and later · before 5.12.4
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 5.10.38-1 | 5.10.38-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47059Feb 29, 2024 · crypto: sun8i-ss - fix result memory leak on error path22Monitor
- ← EarlierCVE-2021-47060Feb 29, 2024 · KVM: Stop looking for coalesced MMIO zones if the bus is destroyed31Monitor
- Later →CVE-2021-47062Feb 29, 2024 · KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs22Monitor
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 | 03c6cccedd3913006744faa252a4da5145299343 | Vendor (CNA) |
| Linux Linux | 2ee3757424be7c1cd1d0bbfa6db29a7edd82a250 | Vendor (CNA) |
| Linux Linux | 30f46c6993731efb2a690c9197c0fd9ed425da2d | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4e899ca848636b37e9ac124bc1723862a7d7d927 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5.9 | Vendor (CNA) |
| debian:linux | 5.10.38-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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0155 · Mar 1, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.