Vulnerability Description
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).
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.15, < 6.18.39 |
References
- https://git.kernel.org/stable/c/6ebf2eb46fbd5b40393ff8fbb847ba96925beaffPatch
- https://git.kernel.org/stable/c/e7b5e55652746b1221b9c10ff80eae8a154101baPatch
- https://git.kernel.org/stable/c/f565297edf316016be4a1a9e2eb9f39359313f43Patch
FAQ
What is CVE-2026-64291?
CVE-2026-64291 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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...
How severe is CVE-2026-64291?
CVE-2026-64291 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-64291?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.