CVE-2026-68324

Received Received - Intake

Buffer Overflow in Linux Kernel iommu/intel

Publication date: 2026-08-10

Last updated on: 2026-08-19

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-08-19

Generated

2026-08-30

AI Q&A

2026-08-10

EPSS Evaluated

2026-08-29

NVD

CVE-2026-68324

EUVD

EUVD-2026-55425

Affected Vendors & Products

Vendor	Product	Version / Range
linux	kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's iommu/intel component. It involves a function called dmar_latency_disable() that incorrectly clears memory. Instead of zeroing out just one specific entry in a latency statistics array, it clears the entire array starting from a miscalculated position. This causes memory corruption when the entry index is greater than zero, potentially leading to system instability or crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's IOMMU Intel driver and involves a memory corruption issue in dmar_latency_disable(). Detection requires checking the kernel version and examining the affected function in the source code. No direct network detection commands are applicable.

Impact Analysis

This vulnerability could cause system crashes or instability on affected Linux systems using Intel IOMMU. It may lead to unexpected behavior, data corruption, or denial of service if exploited. Users running vulnerable kernel versions should apply the provided fix to prevent potential issues.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a memory corruption issue in the Linux kernel's IOMMU subsystem that could lead to system instability or crashes. Compliance impacts would only occur if such failures disrupted data processing or security controls, which is not specified in the provided context.

Mitigation Strategies

Apply the kernel patch that fixes the out-of-bounds memset in dmar_latency_disable(). Update to a patched version of the Linux kernel where this issue is resolved. Monitor vendor advisories for kernel updates.

Hi! I’m here to help you understand CVE-2026-68324. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70