CVE-2026-64292: iommufd: Move vevent memory allocation outside spinlock

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-07-25 · updated 2026-08-17
Weakness: CWE-401

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.

Affected products

Linux kernel: from 6.15 before 6.18.40; from 6.19 before 7.1.4 — fixed in 6.18.40, 7.1.4

How to fix

Upgrade to a fixed version: Linux kernel 6.18.40, 7.1.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-64292 or the next vulnerability affects your stack