LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40058: iommu/vt-d: Disallow dirty tracking if incoherent page walk

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Disallow dirty tracking if incoherent page walk Dirty page tracking relies on the IOMMU atomically updating the dirty bit in the paging-structure entry. For this operation to succeed, the paging- structure memory must be coherent between the IOMMU and the CPU. In another word, if the iommu page walk is incoherent, dirty page tracking doesn't work. The Intel VT-d specification, Section 3.10 "Snoop Behavior" states: "Remapping hardware encountering the need to atomically update A/EA/D bits in a paging-structure entry that is not snooped will result in a non- recoverable fault." To prevent an IOMMU from being incorrectly configured for dirty page tracking when it is operating in an incoherent mode, mark SSADS as supported only when both ecap_slads and ecap_smpwc are supported.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Intel VT-d flaw can allow dirty-page tracking where the IOMMU cannot safely update page-table state. On affected hardware configurations, this can cause a non-recoverable fault and undermine system availability. Exposure requires local, low-privileged access and a specific incoherent page-walk configuration.

Executive priority

Treat as a high-priority infrastructure update for virtualization or other systems using Intel VT-d dirty tracking. Prioritize exposed production hosts, but avoid declaring an emergency solely from the score because no active exploitation is documented.

Technical view

Linux incorrectly permits SSADS dirty tracking without confirming coherent IOMMU page walks. Atomic A/EA/D-bit updates to unsnooped paging structures can produce a non-recoverable fault. The fix exposes SSADS only when both ecap_slads and ecap_smpwc capabilities are present.

Likely exposure

Likely exposure is limited to affected Linux kernels using Intel VT-d IOMMU dirty-page tracking on hardware with incoherent page walks. The supplied affected-version data includes 6.7, 6.12.53, 6.17.3, and 6.18, but its exact range semantics are unclear; distribution backports require separate verification.

Exploitation context

The supplied CVSS is 8.8 and describes local, low-complexity exploitation requiring low privileges and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The core invariant is coherency for atomic IOMMU updates to paging-structure dirty bits. Review capability detection and SSADS gating, especially vendor backports. The supplied version list is ambiguous and contains an unexplained “0,” so commit-level verification is more reliable than version-string matching alone.

Mitigation direction

  • Update to a vendor-supported kernel containing the cited stable fix.
  • Confirm distribution backports through the kernel package changelog or vendor advisory.
  • Until updated, avoid affected dirty-tracking configurations where feasible and vendor-approved.
  • Prioritize hosts using Intel VT-d and IOMMU dirty-page tracking.

Validation and detection

  • Inventory kernel versions and identify systems using Intel VT-d IOMMU functionality.
  • Determine whether dirty-page tracking is enabled on potentially affected hosts.
  • Verify the installed kernel includes one of the cited stable commits or an equivalent backport.
  • Confirm SSADS is exposed only when both ecap_slads and ecap_smpwc are supported.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2025-40058 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
0ADP providers
4Source links

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-2025-40058Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf35f22cc760eb2c7034bf53251399685d611e03f, f35f22cc760eb2c7034bf53251399685d611e03f, f35f22cc760eb2c7034bf53251399685d611e03funaffected
LinuxLinux6.7, 0, 6.12.53, 6.17.3, 6.18affected
Weakness

CWE details

No CWE listed

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