CVE-2026-64292

CVE-2026-64292 : In the Linux kernel, the iommufd component is vulnerable due to veventq memory allocation happening inside a spinlock, enabling a local user to exhaust atomic memory reserves by creating large queues and trigger a DoS. The fix moves the veventq memory allocation outside the spinl...

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

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 queu...

EUVD-2026-49004

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 queu...

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

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 queu...

PT-2026-64513

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description In the iommufd component, memory allocation for veventq occurs inside a spinlock. Because the queue depth is determined by user space, a user can allocate excessively large queues to...