iommufd: Set veventq_depth upper bound
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f565297edf316016be4a1a9e2eb9f39359313f43, Kernel 7.1.4, Kernel e7b5e55652746b1221b9c10ff80eae8a154101ba and 2 more.
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).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e36ba5ab808ef6237c3148d469c8238674230e2b <f565297edf316016be4a1a9e2eb9f39359313f43, >=6.19 <7.1.4, >=e36ba5ab808ef6237c3148d469c8238674230e2b <e7b5e55652746b1221b9c10ff80eae8a154101ba, >=6.15 <6.18.39, =6.15, >=e36ba5ab808ef6237c3148d469c8238674230e2b <6ebf2eb46fbd5b40393ff8fbb847ba96925beaff | f565297edf316016be4a1a9e2eb9f39359313f43, 7.1.4, e7b5e55652746b1221b9c10ff80eae8a154101ba, 6.18.39, 6ebf2eb46fbd5b40393ff8fbb847ba96925beaff |
| linux-kernel: Kernel | >=6.15.0 <6.18.39, >=6.19.0 <7.1.4 | 6.18.39, 7.1.4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket