Answer in brief
CVE-2026-68324 records a Unknown severity vulnerability in iommu/intel: Fix out-of-bounds memset in dmar_latency_disable(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <3078d82e7fe9048a2b90a992e71af7cd7ef881fa || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <866a35735e56b9dc81cbc33899255134adf6d8b3 || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <d06fea9b85f038690f55e72fe0c45e113715a85a || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <0e28ca1c3204b51068579defc904a0dfba5e5c57 || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <754f8efe45f87e3a9c6871b645b2f9d46d1b407b | 3078d82e7fe9048a2b90a992e71af7cd7ef881fa, 866a35735e56b9dc81cbc33899255134adf6d8b3, d06fea9b85f038690f55e72fe0c45e113715a85a, 0e28ca1c3204b51068579defc904a0dfba5e5c57, 754f8efe45f87e3a9c6871b645b2f9d46d1b407b |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68324 records a Unknown severity vulnerability in iommu/intel: Fix out-of-bounds memset in dmar_latency_disable(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <3078d82e7fe9048a2b90a992e71af7cd7ef881fa || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <866a35735e56b9dc81cbc33899255134adf6d8b3 || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <d06fea9b85f038690f55e72fe0c45e113715a85a || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <0e28ca1c3204b51068579defc904a0dfba5e5c57 || >=55ee5e67a59a1b6f388d7a1c7b24022145f47a3e <754f8efe45f87e3a9c6871b645b2f9d46d1b407b | 3078d82e7fe9048a2b90a992e71af7cd7ef881fa, 866a35735e56b9dc81cbc33899255134adf6d8b3, d06fea9b85f038690f55e72fe0c45e113715a85a, 0e28ca1c3204b51068579defc904a0dfba5e5c57, 754f8efe45f87e3a9c6871b645b2f9d46d1b407b |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.