CVE-2021-47094: KVM: x86/mmu: Don't advance iterator after restart due to yielding
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.21% (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 3a0f64de479cae75effb630a2e0a237ca0d0623c, d884eefd75cc54887bc2e9e724207443525dfb2c.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3a0f64de479cae75effb630a2e0a237ca0d0623c, d884eefd75cc54887bc2e9e724207443525dfb2c 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: Don't advance iterator after restart due to yielding After dropping mmu_lock in the TDP MMU, restart the iterator during tdp_iter_next() and do not advance the iterator. Advancing the iterator results in skipping the top-level SPTE and all its children, which is fatal if any of the skipped SPTEs were not visited before yielding. When zapping all SPTEs, i.e. when min_level == root_level, restarting the iter and then invoking tdp_iter_next() is always fatal if the current gfn has as a valid SPTE, as advancing the iterator results in try_step_side() skipping the current gfn, which wasn't visited before yielding. Sprinkle WARNs on iter->yielded being true in various helpers that are often used in conjunction with yielding, and tag the helper with __must_check to reduce the probabily of improper usage. Failing to zap a top-level SPTE manifests in one of two ways. If a valid SPTE is skipped by both kvm_tdp_mmu_zap_all() and kvm_tdp_mmu_put_root(), the shadow page will be leaked and KVM will WARN accordingly. WARNING: CPU: 1 PID: 3509 at arch/x86/kvm/mmu/tdp_mmu.c:46 [kvm] RIP: 0010:kvm_mmu_uninit_tdp_mmu+0x3e/0x50 [kvm] Call Trace: <TASK> kvm_arch_destroy_vm+0x130/0x1b0 [kvm] kvm_destroy_vm+0x162/0x2a0 [kvm] kvm_vcpu_release+0x34/0x60 [kvm] __fput+0x82/0x240 task_work_run+0x5c/0x90 do_exit+0x364/0xa10 ? futex_unqueue+0x38/0x60 do_group_exit+0x33/0xa0 get_signal+0x155/0x850 arch_do_signal_or_restart+0xed/0x750 exit_to_user_mode_prepare+0xc5/0x120 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae If kvm_tdp_mmu_zap_all() skips a gfn/SPTE but that SPTE is then zapped by kvm_tdp_mmu_put_root(), KVM triggers a use-after-free in the form of marking a struct page as dirty/accessed after it has been put back on the free list. This directly triggers a WARN due to encountering a page with page_count() == 0, but it can also lead to data corruption and additional errors in the kernel. WARNING: CPU: 7 PID: 1995658 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:171 RIP: 0010:kvm_is_zone_device_pfn.part.0+0x9e/0xd0 [kvm] Call Trace: <TASK> kvm_set_pfn_dirty+0x120/0x1d0 [kvm] __handle_changed_spte+0x92e/0xca0 [kvm] __handle_changed_spte+0x63c/0xca0 [kvm] __handle_changed_spte+0x63c/0xca0 [kvm] __handle_changed_spte+0x63c/0xca0 [kvm] zap_gfn_range+0x549/0x620 [kvm] kvm_tdp_mmu_put_root+0x1b6/0x270 [kvm] mmu_free_root_page+0x219/0x2c0 [kvm] kvm_mmu_free_roots+0x1b4/0x4e0 [kvm] kvm_mmu_unload+0x1c/0xa0 [kvm] kvm_arch_destroy_vm+0x1f2/0x5c0 [kvm] kvm_put_kvm+0x3b1/0x8b0 [kvm] kvm_vcpu_release+0x4e/0x70 [kvm] __fput+0x1f7/0x8c0 task_work_run+0xf8/0x1a0 do_exit+0x97b/0x2230 do_group_exit+0xda/0x2a0 get_signal+0x3be/0x1e50 arch_do_signal_or_restart+0x244/0x17f0 exit_to_user_mode_prepare+0xcb/0x120 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x4d/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Note, the underlying bug existed even before commit 1af4a96025b3 ("KVM: x86/mmu: Yield in TDU MMU iter even if no SPTES changed") moved calls to tdp_mmu_iter_cond_resched() to the beginning of loops, as KVM could still incorrectly advance past a top-level entry when yielding on a lower-level entry. But with respect to leaking shadow pages, the bug was introduced by yielding before processing the current gfn. Alternatively, tdp_mmu_iter_cond_resched() could simply fall through, or callers could jump to their "retry" label. The downside of that approach is that tdp_mmu_iter_cond_resched() _must_ be called before anything else in the loop, and there's no easy way to enfornce that requirement. Ideally, KVM would handling the cond_resched() fully within the iterator macro (the code is actually quite clean) and avoid this entire class of bugs, but that is extremely difficult do wh ---truncated---
- Published
- Mar 4, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
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
- —
- 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 |
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.10affected
- faaf05b00aecdb347ffd1d763d024394ec0329f8 and later · before d884eefd75cc54887bc2e9e724207443525dfb2caffected · git
- faaf05b00aecdb347ffd1d763d024394ec0329f8 and later · before 3a0f64de479cae75effb630a2e0a237ca0d0623caffected · git
- before 5.10not affected · semver
- 5.15.12 and later · up to and including 5.15.*not affected · semver
- 5.16 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.15.12
- linux linux kernel5.16
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.15.15-1 | 5.15.15-1 |
| openSUSE:Leap 15.5 | dtb-aarch64 | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-64kb | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-debug | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-default | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-default-base | before 5.14.21-150500.55.59.1.150500.6.25.7 | 5.14.21-150500.55.59.1.150500.6.25.7 |
| openSUSE:Leap 15.5 | kernel-docs | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-kvmsmall | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-obs-build | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-obs-qa | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-source | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-syms | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-zfcpdump | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap Micro 5.3 | kernel-default | before 5.14.21-150400.24.116.1 | 5.14.21-150400.24.116.1 |
| openSUSE:Leap Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.116.1.150400.24.54.5 | 5.14.21-150400.24.116.1.150400.24.54.5 |
| openSUSE:Leap Micro 5.3 | kernel-rt | before 5.14.21-150400.15.76.1 | 5.14.21-150400.15.76.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.116.1 | 5.14.21-150400.24.116.1 |
+27
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-47092Mar 4, 2024 · KVM: VMX: Always clear vmx->fail on emulation_required22Monitor
- ← EarlierCVE-2021-47093Mar 4, 2024 · platform/x86: intel_pmc_core: fix memleak on registration failure22Monitor
- Later →CVE-2021-47095Mar 4, 2024 · ipmi: ssif: initialize ssif_info->client early22Monitor
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 | 3a0f64de479cae75effb630a2e0a237ca0d0623c | Vendor (CNA) |
| Linux Linux | d884eefd75cc54887bc2e9e724207443525dfb2c | Vendor (CNA) |
| debian:linux | 5.15.15-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-64kb | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-debug | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-default | 5.14.21-150400.24.116.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-default-base | 5.14.21-150400.24.116.1.150400.24.54.5 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-docs | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-obs-build | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150400.15.76.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.116.1.150400.24.54.5 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_25 | 1-150400.9.5.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_13 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150400.15.76.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150400.15.76.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150400.24.116.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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0167 · Mar 5, 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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.