CVE-2026-68324
iommu/intel: Fix out-of-bounds memset in dmar_latency_disable()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/intel: Fix out-of-bounds memset in dmar_latency_disable() dmar_latency_disable() intends to zero out only the single latency_statistic entry for the given type, but the memset size was computed as sizeof(lstat) DMAR_LATENCY_NUM, which clears the entire array starting from &lstat[type]. When type > 0, this writes beyond the end of the allocated array, corrupting adjacent memory. Fix by using sizeof(*lstat) to clear only the target entry.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.14
References 7
git.kernel.org
- stable/c/80f3605991461679c298ea2045c350ee3cf36de3
- stable/c/104d89cf5b01cb66ff975d91ed42f61b3904df53
- stable/c/3078d82e7fe9048a2b90a992e71af7cd7ef881fa
- stable/c/866a35735e56b9dc81cbc33899255134adf6d8b3
- stable/c/d06fea9b85f038690f55e72fe0c45e113715a85a
- stable/c/0e28ca1c3204b51068579defc904a0dfba5e5c57
- stable/c/754f8efe45f87e3a9c6871b645b2f9d46d1b407b