Out-of-Bounds The advisory has been revoked - it doesn't affect any version of package kernel-rt-64k-debug-devel-matched (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL9-KERNELRT64KDEBUGDEVELMATCHED-13749226
- published29 Oct 2025
- disclosed28 Oct 2025
Introduced: 28 Oct 2025
CVE-2025-40058 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:9.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-64k-debug-devel-matched package and not the kernel-rt-64k-debug-devel-matched package as distributed by RHEL.
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.