iommufd: Avoid locking internal accesses during unmap
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0dbcdf4473a614adbd732d567c9b39ac0e040e0c, Kernel 436189ee4bb2c7c993b945d68570dd38c3e4349e, Kernel 50a66a63d1c841ae6b28a4551f642c1bba4c9529 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: iommufd: Avoid locking internal accesses during unmap iommufd_access_notify_unmap() skips internal accesses because they do not have an external unmap callback to invoke. However, the current test calls iommufd_lock_obj() before checking whether the access is internal. If iommufd_lock_obj() succeeds, the loop then sees the internal access and continues, bypassing the matching iommufd_put_object() used by the normal unmap path. This leaks the object reference taken by iommufd_lock_obj(). Check for internal accesses first so skipped entries are never locked.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <0dbcdf4473a614adbd732d567c9b39ac0e040e0c, >=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <436189ee4bb2c7c993b945d68570dd38c3e4349e, >=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <50a66a63d1c841ae6b28a4551f642c1bba4c9529 | 0dbcdf4473a614adbd732d567c9b39ac0e040e0c, 436189ee4bb2c7c993b945d68570dd38c3e4349e, 50a66a63d1c841ae6b28a4551f642c1bba4c9529 |
| linux-kernel: Kernel | >=6.17.0 <6.18.50, >=6.19.0 <7.2.4 | 6.18.50, 7.2.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