CVE-2025-40058
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-10-28

Last updated on: 2025-10-30

Assigner: kernel.org

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-28
Last Modified
2025-10-30
Generated
2026-05-07
AI Q&A
2025-10-28
EPSS Evaluated
2026-05-05
NVD
CVE-2025-40058
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability involves the Linux kernel's handling of dirty page tracking in the IOMMU (Input-Output Memory Management Unit) when using Intel VT-d technology. Dirty page tracking depends on the IOMMU atomically updating the dirty bit in paging-structure entries, which requires coherent memory between the IOMMU and the CPU. If the IOMMU page walk is incoherent, dirty page tracking fails. According to the Intel VT-d specification, attempting to atomically update bits in a paging-structure entry that is not snooped (i.e., incoherent) causes a non-recoverable fault. The fix prevents the IOMMU from being incorrectly configured for dirty page tracking in incoherent mode by marking SSADS as supported only when certain conditions (ecap_slads and ecap_smpwc support) are met.


How can this vulnerability impact me? :

If this vulnerability is exploited or triggered, it can cause non-recoverable faults in the system's memory management related to IOMMU operations. This could lead to system instability, crashes, or failures in memory tracking mechanisms, potentially affecting system reliability and performance.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart