Answer in brief
CVE-2026-64291 records a Medium severity (CVSS 5.5) vulnerability in iommufd: Set veventq_depth upper bound. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e36ba5ab808ef6237c3148d469c8238674230e2b <f565297edf316016be4a1a9e2eb9f39359313f43 || >=e36ba5ab808ef6237c3148d469c8238674230e2b <e7b5e55652746b1221b9c10ff80eae8a154101ba || >=e36ba5ab808ef6237c3148d469c8238674230e2b <6ebf2eb46fbd5b40393ff8fbb847ba96925beaff | f565297edf316016be4a1a9e2eb9f39359313f43, e7b5e55652746b1221b9c10ff80eae8a154101ba, 6ebf2eb46fbd5b40393ff8fbb847ba96925beaff |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
In the Linux kernel, the following vulnerability has been resolved: iommufd: Set veventq_depth upper bound iommufd_veventq_alloc() accepts any !0 veventq_depth from userspace, with an upper bound at U32_MAX. This leaves a vulnerability where userspace can allocate excessively large queues to exhaust kernel memory reserves. Cap the veventq_depth (maximum number of entries) to 1 << 19, matching the maximum number of entries in the SMMUv3 EVTQ (the largest use case today).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64291 records a Medium severity (CVSS 5.5) vulnerability in iommufd: Set veventq_depth upper bound. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e36ba5ab808ef6237c3148d469c8238674230e2b <f565297edf316016be4a1a9e2eb9f39359313f43 || >=e36ba5ab808ef6237c3148d469c8238674230e2b <e7b5e55652746b1221b9c10ff80eae8a154101ba || >=e36ba5ab808ef6237c3148d469c8238674230e2b <6ebf2eb46fbd5b40393ff8fbb847ba96925beaff | f565297edf316016be4a1a9e2eb9f39359313f43, e7b5e55652746b1221b9c10ff80eae8a154101ba, 6ebf2eb46fbd5b40393ff8fbb847ba96925beaff |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
In the Linux kernel, the following vulnerability has been resolved: iommufd: Set veventq_depth upper bound iommufd_veventq_alloc() accepts any !0 veventq_depth from userspace, with an upper bound at U32_MAX. This leaves a vulnerability where userspace can allocate excessively large queues to exhaust kernel memory reserves. Cap the veventq_depth (maximum number of entries) to 1 << 19, matching the maximum number of entries in the SMMUv3 EVTQ (the largest use case today).
Quoted source text, attributed separately from HOL analysis.