drm/panfrost: Job should reference MMU not file_priv
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| 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/panfrost: Job should reference MMU not file_priv
For a while now it's been allowed for a MMU context to outlive it's corresponding panfrost_priv, however the job structure still references panfrost_priv to get hold of the MMU context. If panfrost_priv has been freed this is a use-after-free which I've been able to trigger resulting in a splat.
To fix this, drop the reference to panfrost_priv in the job structure and add a direct reference to the MMU structure which is what's actually needed.
From the CVE record · Linux
A panfrost job can reference a freed private structure when an MMU context outlives it, causing a use-after-free. This has been triggered to produce a kernel splat; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the panfrost driver should check their versions; affected versions are not specified.