iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f41d317be00767e81ce0a664fa37ab829654ab8d, Kernel 63ff69e265bec1712d2b7105e7c1556f73a3080f, Kernel dd2f8565e68cac312451926ce2e3883923caf081 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA Generally userspace is going to step the dirty bitmap through the IOVA space. However if the bitmap ends in the middle of a large PTE this is problematic. The first step will clear the dirty bit and report dirty to the end of its bitmap while the second step will see the clear'd dirty and report clean for the start of the bitmap. If it happens this ends up losing dirties. Further this function is missing bounds checking so if this does happen ther is a good chance it will write memory beyond what the userspace was expecting. Return an error code if this illegal condition happens.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 <f41d317be00767e81ce0a664fa37ab829654ab8d, >=58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 <63ff69e265bec1712d2b7105e7c1556f73a3080f, >=58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 <dd2f8565e68cac312451926ce2e3883923caf081, >=58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 <e21952d72b4740f08a272d694cca223b6b0099ca, =6.1 | f41d317be00767e81ce0a664fa37ab829654ab8d, 63ff69e265bec1712d2b7105e7c1556f73a3080f, dd2f8565e68cac312451926ce2e3883923caf081, e21952d72b4740f08a272d694cca223b6b0099ca |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=6.1.0 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket