In the Linux kernel, the following vulnerability has been resolved:
drm/panfrost: Fix GEM handle creation ref-counting
panfrost_gem_create_with_handle() previously returned a BO but with the
only reference being from the handle, which user space could in theory
guess and release, causing a use-after-free. Additionally if the call to
panfrost_gem_mapping_get() in panfrost_ioctl_create_bo() failed then
a(nother) reference on the BO was dropped.
The _create_with_handle() is a problematic pattern, so ditch it and
instead create the handle in panfrost_ioctl_create_bo(). If the call to
panfrost_gem_mapping_get() fails then this means that user space has
indeed gone behind our back and freed the handle. In which case just
return an error code.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s Panfrost graphics driver can let a low-privileged local user trigger use-after-free memory corruption. Successful exploitation could compromise data, system integrity, or availability. The issue is not remotely exploitable according to the supplied CVSS vector.
Executive priority
Treat as a high-priority local privilege-boundary issue on systems using Panfrost, especially where untrusted users can execute code. First confirm driver and kernel exposure because systems without the affected driver path are unlikely to be reachable. Remediate through supported kernel updates.
Technical view
Incorrect GEM buffer-object reference counting allowed userspace to release a guessed handle while the kernel still used the object. A related mapping-failure path could drop another reference. The correction moves handle creation into panfrost_ioctl_create_bo() and returns an error when the handle was already freed.
Likely exposure
Exposure requires an affected Linux kernel, the Panfrost driver, and local low-privileged access. The bundle lists 5.2, 5.10.163, 5.15.87, 6.0.19, 6.1.5, and 6.2 as affected, but provides incomplete version-range semantics; the listed “0” is ambiguous.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle marks KEV false and provides no evidence of active exploitation or a public exploit. KEV absence does not prove exploitation has never occurred.
Researcher notes
CWE-416 and the description support a use-after-free classification caused by GEM handle ownership and reference-counting errors. Exact affected and fixed release boundaries are not fully represented in the bundle. The five stable-kernel commits are the strongest supplied indicators for backport verification; exploitability has not been independently demonstrated here.
Mitigation direction
Apply a vendor kernel update incorporating the applicable referenced stable fix.
Check distribution advisories for corrected package versions and required restart guidance.
Prioritize multi-user or otherwise untrusted systems using the Panfrost driver.
If no update is available, request vendor-supported mitigation guidance.
Validation and detection
Inventory running kernel versions and identify systems where the Panfrost driver is present or active.
Compare vendor package changelogs or kernel source against the referenced fix commits.
After updating, verify the running kernel contains the applicable correction.
Reassess local-user access on exposed systems until remediation is confirmed.
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.
2CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.