drm/panthor: Fix UAF on kernel BO VA nodes
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/panthor: Fix UAF on kernel BO VA nodes
If the MMU is down, panthor_vm_unmap_range() might return an error. We expect the page table to be updated still, and if the MMU is blocked, the rest of the GPU should be blocked too, so no risk of accessing physical memory returned to the system (which the current code doesn't cover for anyway).
Proceed with the rest of the cleanup instead of bailing out and leaving the va_node inserted in the drm_mm, which leads to UAF when other adjacent nodes are removed from the drm_mm tree.
From the CVE record · Linux
The Linux kernel’s drm/panthor driver can leave a VA node in its management tree when unmapping fails while the MMU is down. Removing adjacent nodes can then trigger a use-after-free. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with the drm/panthor driver should check whether their kernel is affected; affected versions are not specified.