Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2026-68324
- https://git.kernel.org/stable/c/0e28ca1c3204b51068579defc904a0dfba5e5c57
- https://git.kernel.org/stable/c/104d89cf5b01cb66ff975d91ed42f61b3904df53
- https://git.kernel.org/stable/c/3078d82e7fe9048a2b90a992e71af7cd7ef881fa
- https://git.kernel.org/stable/c/754f8efe45f87e3a9c6871b645b2f9d46d1b407b
- https://git.kernel.org/stable/c/80f3605991461679c298ea2045c350ee3cf36de3
- https://git.kernel.org/stable/c/866a35735e56b9dc81cbc33899255134adf6d8b3
- https://git.kernel.org/stable/c/d06fea9b85f038690f55e72fe0c45e113715a85a
EPSS
CVE ID
Связанные уязвимости
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.
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.
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.
iommu/intel: Fix out-of-bounds memset in dmar_latency_disable()
In the Linux kernel, the following vulnerability has been resolved: i ...
EPSS