CVE-2026-64291
CVE CVE-2026-64291EUVD EUVD-2026-49003Published 2026-07-25T08:49:30.000Z
What the advisory describes
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).
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux e36ba5ab808ef6237c3148d469c8238674230e2b <e7b5e55652746b1221b9c10ff80eae8a154101ba; 6.15; patch: 7.1.4; e36ba5ab808ef6237c3148d469c8238674230e2b <f565297edf316016be4a1a9e2eb9f39359313f43; patch: 7.2-rc1; patch: 6.18.39; patch: 0; e36ba5ab808ef6237c3148d469c8238674230e2b <6ebf2eb46fbd5b40393ff8fbb847ba96925beaff
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.