CVE-2021-47639: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU
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.25% (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 0c8a8da182d4333d9bbb9131d765145568c847b2, 8cf6f98ab1d16d5e607635a0c21c4231eb15367e, af47248407c0c5ae52a752af1ab5ce5b0db91502.
Low priority for now. Upgrade to Linux Linux 0c8a8da182d4333d9bbb9131d765145568c847b2, 8cf6f98ab1d16d5e607635a0c21c4231eb15367e, af47248407c0c5ae52a752af1ab5ce5b0db91502 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: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU Zap both valid and invalid roots when zapping/unmapping a gfn range, as KVM must ensure it holds no references to the freed page after returning from the unmap operation. Most notably, the TDP MMU doesn't zap invalid roots in mmu_notifier callbacks. This leads to use-after-free and other issues if the mmu_notifier runs to completion while an invalid root zapper yields as KVM fails to honor the requirement that there must be _no_ references to the page after the mmu_notifier returns. The bug is most easily reproduced by hacking KVM to cause a collision between set_nx_huge_pages() and kvm_mmu_notifier_release(), but the bug exists between kvm_mmu_notifier_invalidate_range_start() and memslot updates as well. Invalidating a root ensures pages aren't accessible by the guest, and KVM won't read or write page data itself, but KVM will trigger e.g. kvm_set_pfn_dirty() when zapping SPTEs, and thus completing a zap of an invalid root _after_ the mmu_notifier returns is fatal. WARNING: CPU: 24 PID: 1496 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:173 [kvm] RIP: 0010:kvm_is_zone_device_pfn+0x96/0xa0 [kvm] Call Trace: <TASK> kvm_set_pfn_dirty+0xa8/0xe0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] zap_gfn_range+0x1f3/0x310 [kvm] kvm_tdp_mmu_zap_invalidated_roots+0x50/0x90 [kvm] kvm_mmu_zap_all_fast+0x177/0x1a0 [kvm] set_nx_huge_pages+0xb4/0x190 [kvm] param_attr_store+0x70/0x100 module_attr_store+0x19/0x30 kernfs_fop_write_iter+0x119/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1cc/0x270 ksys_write+0x5f/0xe0 do_syscall_64+0x38/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK>
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
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
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13 and later · before 5.15.33
- linux linux kernel5.16 and later · before 5.16.19
- linux linux kernel5.17 and later · before 5.17.2
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
- 5.13affected
- b7cccd397f310739fb85383033e95580f99927e0 and later · before af47248407c0c5ae52a752af1ab5ce5b0db91502affected · git
- b7cccd397f310739fb85383033e95580f99927e0 and later · before 0c8a8da182d4333d9bbb9131d765145568c847b2affected · git
- b7cccd397f310739fb85383033e95580f99927e0 and later · before 8cf6f98ab1d16d5e607635a0c21c4231eb15367eaffected · git
- b7cccd397f310739fb85383033e95580f99927e0 and later · before d62007edf01f5c11f75d0f4b1e538fc52a5b1982affected · git
- before 5.13not affected · semver
- 5.15.33 and later · up to and including 5.15.*not affected · semver
- 5.16.19 and later · up to and including 5.16.*not affected · semver
- 5.17.2 and later · up to and including 5.17.*not affected · semver
- 5.18 and laternot affected · original_commit_for_fix
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.17.3-1 | 5.17.3-1 |
| Red Hat:enterprise_linux:8::baseos | bpftool | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | bpftool-debuginfo | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-abi-stablelists | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-core | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-core | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-debuginfo | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-devel | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules-extra | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-aarch64 | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-ppc64le | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-s390x | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-devel | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-doc | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules-extra | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-debuginfo | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-libs | before 0:4.18.0-425.3.1.el8 | 0:4.18.0-425.3.1.el8 |
+70
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-47637Feb 26, 2025 · ubifs: Fix deadlock in concurrent rename whiteout and inode writeback22Monitor
- ← EarlierCVE-2021-47638Feb 26, 2025 · ubifs: rename_whiteout: Fix double free for whiteout_ui->data22Monitor
- Later →CVE-2021-47640Feb 26, 2025 · powerpc/kasan: Fix early region not updated correctly31Monitor
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 | 0c8a8da182d4333d9bbb9131d765145568c847b2 | Vendor (CNA) |
| Linux Linux | 8cf6f98ab1d16d5e607635a0c21c4231eb15367e | Vendor (CNA) |
| Linux Linux | af47248407c0c5ae52a752af1ab5ce5b0db91502 | Vendor (CNA) |
| Linux Linux | d62007edf01f5c11f75d0f4b1e538fc52a5b1982 | Vendor (CNA) |
| debian:linux | 5.17.3-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-425.3.1.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.158.1.150400.24.78.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_38 | 1-150400.9.3.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_25 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.91.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.91.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150400.24.158.1 · SUSE:Linux Enterprise Server 15 SP4-LTSS | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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-secondary
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
- 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.