CVE-2026-64292 Details
Description
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.
A vulnerability exists in the Linux kernel's IOMMUFD (I/O Memory Management Unit Fault Detection) handling, specifically within the vevent queue memory allocation process. This allocation occurs inside a spinlock, creating a risk that user space can manipulate queue depths to exhaust atomic memory reserves. The vulnerability has been addressed by moving the memory allocation outside of the spinlock and utilizing GFP_NOWAIT, allowing the allocation to fail quickly under memory pressure without interfering with GFP_ATOMIC reserves or reclaiming memory from the IRQ handler. In cases of allocation failure, the system now queues a header to inform user space of the dropped event and returns an error code, indicating kernel-side memory pressure. This change is part of a broader effort to manage event queue depths more effectively.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/47443565d10c51366c9382dbc8597cd6c460b8a2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6c5fc40200cd0a87d66a368eee00df4d1cca946e | kernel.org | Patch |
| https://git.kernel.org/stable/c/779480ea79551c31964e74b9aef0e730faa3aa11 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-401 | Missing Release of Memory after Effective Lifetime | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.15, < 6.18.40 >= 6.19, < 7.1.4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 17, 2026 | CVE Modified | kernel.org |
| Aug 12, 2026 | Initial Analysis | [email protected] |
| Jul 25, 2026 | New CVE Received | kernel.org |