iommu/sva: Set handle->dev before the SVA handle is visible
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommu/sva: Set handle->dev before the SVA handle is visible
iommu_attach_device_pasid() installs the new SVA attach handle in the group PASID lookup before iommu_sva_bind_device() returns. A concurrent bind can therefore find and reuse the same handle after iommu_sva_lock is dropped.
handle->dev was initialized after dropping iommu_sva_lock. This leaves a window where a racing bind can return a handle whose dev pointer is still NULL. A subsequent iommu_sva_unbind_device() can then dereference it via handle->dev->iommu_group.
Initialize handle->dev before releasing iommu_sva_lock so any visible SVA handle is fully initialized.
From the CVE record · Linux
The Linux kernel can make an SVA handle visible to a concurrent bind before its device pointer is initialized. If a racing bind reuses that handle, a subsequent unbind can dereference the NULL pointer. The input does not establish whether an attacker can trigger this remotely or locally, or what access would be required.
Engineers running the Linux kernel should check their versions for this issue; affected versions were not provided.