CVE-2022-49359

drm/panfrost: Job should reference MMU not file_priv

HIGH
7.8
CVSS Score
Published: February 26, 2025 at 02:11 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.10.67v ≥ 5.13.19v ≥ 5.14.65.10.67 ≤ v < 5.115.13.19 ≤ v < 5.145.14.6 ≤ v < 5.155.14.6 ≤ v < 5.17.155.15 ≤ v < 5.17.155.15 ≤ v < 5.18.45.15 ≤ v < 5.195.18 ≤ v < 5.18.45.10.675.13.195.14.65.19 rc1626adede2642f00c8918999a2451bd0a644ab9b77fdc48cc63a30fa3480d18bdd8c5fff2b9b15212c29485e34e63198dca6289639aa711f99d88e76ecf461fa9250a634e8afc4433d82ae0decea8136e
Vendor states this is fixed in 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2 (fixed)
Vendor states this is fixed in 6e516faf04317db2c46cbec4e3b78b4653a5b109 (fixed)
Vendor states this is fixed in 8c8e8cc91a6ffc79865108279a74fd57d9070a17 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.14, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.17.15 (unaffected)
Vendor states this is fixed in 5.18.4 (unaffected)
Vendor states this is fixed in 5.19 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/472dd7ea5e19a1aeabf1711ddc756777e05ee7c2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6e516faf04317db2c46cbec4e3b78b4653a5b109
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8c8e8cc91a6ffc79865108279a74fd57d9070a17

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card