LiveActive security incident?Get immediate response
CVE Record

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

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]

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux KVM flaw can omit changes made by a nested virtual machine from the host’s dirty-memory log. Systems relying on that log may process an incomplete view of changed memory. The issue requires a specific nested-virtualization configuration and does not automatically affect every Linux host.

Executive priority

Treat this as a high-priority virtualization integrity issue, especially for multi-tenant or nested-KVM environments. Patch exposed hosts through normal emergency maintenance processes after confirming vendor packages. Hosts without KVM, nested virtualization, or the required MMU conditions are lower priority. There is no supplied evidence of active exploitation.

Technical view

KVM’s x86 TDP MMU failed to apply role-specific write protection when clearing dirty bits. With an L2 guest running while L1 has disabled EPT and PML is enabled, L2 SPTEs could remain writable even though KVM disables PML for L2. Consequently, L2 writes might not appear in the dirty log.

Likely exposure

Potentially exposed systems are x86 Linux KVM hosts using TDP MMU and nested virtualization under the described L2, EPT, and PML conditions. The supplied record marks Linux versions including 6.4, 6.6.29, 6.8.8, and 6.9 as affected, but its version data is incomplete or ambiguous.

Exploitation context

The CVSS vector describes local, low-privilege access with no user interaction. However, the supplied sources document incorrect dirty logging, not a demonstrated attack chain. The record is not in KEV, and no cited source establishes active exploitation or public weaponization.

Researcher notes

The observable defect is missing dirty-log accounting rather than a directly documented memory-corruption primitive. Impact depends on how management software consumes KVM dirty logs. The supplied CVSS claims confidentiality, integrity, and availability impact, but the narrative does not establish those consequences or provide a demonstrated exploit path. Affected-version boundaries require vendor confirmation.

Mitigation direction

  • Apply a vendor-supported kernel containing the referenced KVM fix or an equivalent backport.
  • Review Linux distribution advisories to identify the corrected package for each deployed release.
  • Prioritize KVM hosts that permit nested virtualization or run potentially untrusted guests.
  • Follow vendor guidance where package or fixed-version status remains unclear.

Validation and detection

  • Inventory running kernel versions on x86 KVM hosts and compare them with distribution advisories.
  • Determine whether TDP MMU, nested virtualization, L2 operation, EPT, and PML conditions are present.
  • Confirm the installed kernel contains the referenced fix or a documented vendor backport.
  • After updating, verify L2 writes appear in KVM dirty logs using a controlled defensive test.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26990 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-26990Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5982a5392663b30f57ee90b0372c19a7e9cb655a, 5982a5392663b30f57ee90b0372c19a7e9cb655a, 5982a5392663b30f57ee90b0372c19a7e9cb655aunaffected
LinuxLinux6.4, 0, 6.6.29, 6.8.8, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.