Answer in brief
CVE-2025-40058 records a High severity (CVSS 8.8) vulnerability in iommu/vt-d: Disallow dirty tracking if incoherent page walk. 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.
CVSS is 8.8. 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 | >=f35f22cc760eb2c7034bf53251399685d611e03f <ebe16d245a00626bb87163862a1b07daf5475a3e || >=f35f22cc760eb2c7034bf53251399685d611e03f <8d096ce0e87bdc361f0b25d7943543bc53aa0b9e || >=f35f22cc760eb2c7034bf53251399685d611e03f <57f55048e564dedd8a4546d018e29d6bbfff0a7e | ebe16d245a00626bb87163862a1b07daf5475a3e, 8d096ce0e87bdc361f0b25d7943543bc53aa0b9e, 57f55048e564dedd8a4546d018e29d6bbfff0a7e |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 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: 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.
Quoted source text, attributed separately from HOL analysis.