CVE-2022-49359: drm/panfrost: Job should reference MMU not file_priv
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.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49359 is a Linux kernel use-after-free in the Panfrost DRM GPU driver. A local user could potentially affect confidentiality, integrity, and availability on systems using vulnerable kernel builds. The available sources describe an upstream fix, but do not cite active exploitation.
Executive priority
Treat as high priority for Linux fleets using Panfrost-capable kernels, especially shared devices or systems running untrusted local workloads. Patch through normal kernel update channels after confirming exposure.
Technical view
The Panfrost job structure referenced panfrost_priv to reach the MMU context even though the MMU could outlive panfrost_priv. If panfrost_priv was freed first, job handling could dereference freed memory. The fix stores a direct reference to the MMU structure instead.
Likely exposure
Exposure is most likely on Linux systems with affected kernel versions and the drm/panfrost driver enabled. The source bundle lists Linux 5.15, 5.17.15, 5.18.4, and 5.19 as affected data points; verify against vendor kernel packaging and backports.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with high confidentiality, integrity, and availability impact. The source bundle says KEV is false and provides no cited evidence of exploitation in the wild.
Researcher notes
Evidence is limited to the CVE record and upstream stable commit references. The root cause is a lifetime mismatch between panfrost_priv and the MMU context. No public exploit status, affected downstream distributions, or vendor-specific mitigations are provided in the source bundle.
Mitigation direction
Update to a vendor-supported kernel containing the upstream Panfrost MMU reference fix.
Check Linux distribution advisories for affected package versions and backported patches.
Prioritize systems where untrusted local users or workloads can access GPU functionality.
If vendor-supported, reduce exposure by removing unused vulnerable Panfrost-enabled kernels.
Validation and detection
Inventory Linux kernel versions and confirm whether drm/panfrost is present or enabled.
Map installed kernels to vendor advisories or the referenced stable commits.
For source-built kernels, confirm jobs reference the MMU directly, not panfrost_priv.
Review kernel logs for Panfrost-related use-after-free splats as supporting evidence only.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.