CVE-2024-26990

KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status

MEDIUM
5.5
CVSS Score
Published: May 1, 2024 at 05:27 AM UTC
Updated: August 5, 2026 at 12:04 PM 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.4 ≤ v < 6.6.296.4 ≤ v < 6.8.86.4 ≤ v < 6.96.7 ≤ v < 6.8.85982a5392663b30f57ee90b0372c19a7e9cb655a6.9 rc16.9 rc26.9 rc36.9 rc4
Vendor states this is fixed in 2673dfb591a359c75080dd5af3da484b89320d22 (fixed)
Vendor states this is fixed in cdf811a937471af2d1facdf8ae80e5e68096f1ed (fixed)
Vendor states this is fixed in e20bff0f1b2de9cfe303dd35ff46470104a87404 (fixed)
Vendor states this is fixed in 6.4 (unaffected)
Vendor states this is fixed in 6.6.29 (unaffected)
Vendor states this is fixed in 6.8.8 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

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