CVE-2022-49359: drm/panfrost: Job should reference MMU not file_priv

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-02-26 · updated 2026-06-17
Weakness: CWE-416

Description

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.

Affected products

Linux kernel: from 5.10.67 before 5.11; from 5.13.19 before 5.14; from 5.14.6 before 5.17.15; from 5.18 before 5.18.4; 5.19-rc1 — fixed in 5.11, 5.14, 5.17.15, 5.18.4

How to fix

Upgrade to a fixed version: Linux kernel 5.11, 5.14, 5.17.15, 5.18.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-49359 or the next vulnerability affects your stack