Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Disallow dirty tracking if incoherent page walk Dirty page tracking… (CVE-2025-40058)
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.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2025-40058 concerns the iommu/vt-d component's handling of dirty page tracking. Dirty page tracking depends on the IOMMU atomically updating the dirty bit in paging-structure entries, which requires coherent memory between the IOMMU and CPU. If the page walk is incoherent, dirty page tracking fails and can cause faults as per Intel VT-d specification Section 3.10. The vulnerability is mitigated by restricting SSADS support to cases where both ecap_slads and ecap_smpwc features are supported, ensuring proper hardware coherence before enabling dirty tracking.
Potential Impact
If exploited, this vulnerability can lead to high confidentiality, integrity, and availability impacts due to incorrect dirty page tracking and potential non-recoverable faults in the IOMMU. This can disrupt memory management and system stability on affected Linux kernel systems using VT-d with incoherent page walks.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to prevent enabling dirty page tracking when the IOMMU page walk is incoherent by marking SSADS as supported only when both ecap_slads and ecap_smpwc are supported. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly stated here; check the Linux kernel vendor advisory for the latest remediation guidance.
Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Disallow dirty tracking if incoherent page walk Dirty page tracking… (CVE-2025-40058)
Description
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.
CVSS v3.1
Score 8.8high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2025-40058 concerns the iommu/vt-d component's handling of dirty page tracking. Dirty page tracking depends on the IOMMU atomically updating the dirty bit in paging-structure entries, which requires coherent memory between the IOMMU and CPU. If the page walk is incoherent, dirty page tracking fails and can cause faults as per Intel VT-d specification Section 3.10. The vulnerability is mitigated by restricting SSADS support to cases where both ecap_slads and ecap_smpwc features are supported, ensuring proper hardware coherence before enabling dirty tracking.
Potential Impact
If exploited, this vulnerability can lead to high confidentiality, integrity, and availability impacts due to incorrect dirty page tracking and potential non-recoverable faults in the IOMMU. This can disrupt memory management and system stability on affected Linux kernel systems using VT-d with incoherent page walks.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to prevent enabling dirty page tracking when the IOMMU page walk is incoherent by marking SSADS as supported only when both ecap_slads and ecap_smpwc are supported. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly stated here; check the Linux kernel vendor advisory for the latest remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hwfw-95mf-c924
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40058"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d79c2644c7f847b207
Added to database: 07/30/2026, 15:50:47 UTC
Last enriched: 07/30/2026, 16:22:28 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 23
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.