Menu

Star on GitHub · 3.2k

CVE-2026-68324

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 late…

Published Aug 10, 2026EPSS 0.17%

Overview

CVE-2026-68324 is a known-severity vulnerability. It was published on August 10, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-68324?

CVE-2026-68324 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68324?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68324?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68324?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68324 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.