The dmar_latency_disable function, used to reset latency statistics for Intel IOMMU devices, mistakenly cleared a block of memory larger than intended. By calculating the memset size as the product of the entry size and the number of latency statistics, the code zeroed the target entry and also overwritten the following entries in the array. This out‑of‑bounds write corrupts adjacent memory and can lead to unpredictable kernel behavior, including crashes or data integrity issues. While the description does not explicitly state arbitrary code execution, corrupting kernel memory could allow a privileged attacker to influence system behavior or elevate privileges.

All Linux kernel versions that include the iommu/intel driver prior to the commit that fixed the overflow run risk of this vulnerability. The affected product is the Linux kernel itself; specific distribution or version information is not supplied, so any kernel that has not yet incorporated the patch is potentially exposed.

The vulnerability has an EPSS score of < 1% and is not listed in the CISA KEV catalog. Exploitation would require that an attacker can trigger the dmar_latency_disable routine with a non‑zero type value, which is likely limited to privileged kernel context or to a mechanism that allows interface with the IOMMU subsystem. Accordingly, the risk is that a local attacker with kernel privileges could cause memory corruption, potentially leading to denial of service or privilege escalation. The CVSS score of 5.7 indicates a moderate severity.