Answer in brief
CVE-2026-64292 records a Medium severity (CVSS 5.5) vulnerability in iommufd: Move vevent memory allocation outside spinlock. 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 <779480ea79551c31964e74b9aef0e730faa3aa11 || >=e36ba5ab808ef6237c3148d469c8238674230e2b <6c5fc40200cd0a87d66a368eee00df4d1cca946e || >=e36ba5ab808ef6237c3148d469c8238674230e2b <47443565d10c51366c9382dbc8597cd6c460b8a2 | 779480ea79551c31964e74b9aef0e730faa3aa11, 6c5fc40200cd0a87d66a368eee00df4d1cca946e, 47443565d10c51366c9382dbc8597cd6c460b8a2 |
| 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: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queues to exhaust atomic memory reserves. Move the allocation outside the spinlock and use GFP_NOWAIT, which can fail fast under memory pressure without dipping into the GFP_ATOMIC reserves or direct-reclaiming from the threaded IRQ handler. On allocation failure, queue the lost_events_header (so userspace learns of the drop) and return -ENOMEM so the caller learns of the kernel-side memory pressure. This is intentionally distinct from the queue-overflow path, which also queues the lost_events_header but returns 0: a full queue is an expected userspace-pacing condition rather than a kernel error. A subsequent change will cap the upper bound of the veventq_depth.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64292 records a Medium severity (CVSS 5.5) vulnerability in iommufd: Move vevent memory allocation outside spinlock. 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 <779480ea79551c31964e74b9aef0e730faa3aa11 || >=e36ba5ab808ef6237c3148d469c8238674230e2b <6c5fc40200cd0a87d66a368eee00df4d1cca946e || >=e36ba5ab808ef6237c3148d469c8238674230e2b <47443565d10c51366c9382dbc8597cd6c460b8a2 | 779480ea79551c31964e74b9aef0e730faa3aa11, 6c5fc40200cd0a87d66a368eee00df4d1cca946e, 47443565d10c51366c9382dbc8597cd6c460b8a2 |
| 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: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queues to exhaust atomic memory reserves. Move the allocation outside the spinlock and use GFP_NOWAIT, which can fail fast under memory pressure without dipping into the GFP_ATOMIC reserves or direct-reclaiming from the threaded IRQ handler. On allocation failure, queue the lost_events_header (so userspace learns of the drop) and return -ENOMEM so the caller learns of the kernel-side memory pressure. This is intentionally distinct from the queue-overflow path, which also queues the lost_events_header but returns 0: a full queue is an expected userspace-pacing condition rather than a kernel error. A subsequent change will cap the upper bound of the veventq_depth.
Quoted source text, attributed separately from HOL analysis.