iommufd: Avoid locking internal accesses during unmap
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.507.2.47.3In 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.
From the CVE record · Linux
In the Linux kernel, iommufd unmap can leak an object reference when it encounters an internal access. The input does not establish whether an attacker can trigger this behavior or specify any network, authentication, or user-interaction conditions.
Engineers running Linux kernels with iommufd should check their versions against the vendor advisory; affected versions were not provided.