Answer in brief
CVE-2024-26990 records a Unknown severity vulnerability in KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-26990 records a Unknown severity vulnerability in KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5982a5392663b30f57ee90b0372c19a7e9cb655a <cdf811a937471af2d1facdf8ae80e5e68096f1ed || >=5982a5392663b30f57ee90b0372c19a7e9cb655a <e20bff0f1b2de9cfe303dd35ff46470104a87404 || >=5982a5392663b30f57ee90b0372c19a7e9cb655a <2673dfb591a359c75080dd5af3da484b89320d22 | cdf811a937471af2d1facdf8ae80e5e68096f1ed, e20bff0f1b2de9cfe303dd35ff46470104a87404, 2673dfb591a359c75080dd5af3da484b89320d22 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status Check kvm_mmu_page_ad_need_write_protect() when deciding whether to write-protect or clear D-bits on TDP MMU SPTEs, so that the TDP MMU accounts for any role-specific reasons for disabling D-bit dirty logging. Specifically, TDP MMU SPTEs must be write-protected when the TDP MMU is being used to run an L2 (i.e. L1 has disabled EPT) and PML is enabled. KVM always disables PML when running L2, even when L1 and L2 GPAs are in the some domain, so failing to write-protect TDP MMU SPTEs will cause writes made by L2 to not be reflected in the dirty log. [sean: massage shortlog and changelog, tweak ternary op formatting]
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5982a5392663b30f57ee90b0372c19a7e9cb655a <cdf811a937471af2d1facdf8ae80e5e68096f1ed || >=5982a5392663b30f57ee90b0372c19a7e9cb655a <e20bff0f1b2de9cfe303dd35ff46470104a87404 || >=5982a5392663b30f57ee90b0372c19a7e9cb655a <2673dfb591a359c75080dd5af3da484b89320d22 | cdf811a937471af2d1facdf8ae80e5e68096f1ed, e20bff0f1b2de9cfe303dd35ff46470104a87404, 2673dfb591a359c75080dd5af3da484b89320d22 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status Check kvm_mmu_page_ad_need_write_protect() when deciding whether to write-protect or clear D-bits on TDP MMU SPTEs, so that the TDP MMU accounts for any role-specific reasons for disabling D-bit dirty logging. Specifically, TDP MMU SPTEs must be write-protected when the TDP MMU is being used to run an L2 (i.e. L1 has disabled EPT) and PML is enabled. KVM always disables PML when running L2, even when L1 and L2 GPAs are in the some domain, so failing to write-protect TDP MMU SPTEs will cause writes made by L2 to not be reflected in the dirty log. [sean: massage shortlog and changelog, tweak ternary op formatting]
Quoted source text, attributed separately from HOL analysis.