CVE-2024-50174: drm/panthor: Fix race when converting group handle to group object
In the Linux kernel, the following vulnerability has been resolved:
drm/panthor: Fix race when converting group handle to group object
XArray provides it's own internal lock which protects the internal array
when entries are being simultaneously added and removed. However there
is still a race between retrieving the pointer from the XArray and
incrementing the reference count.
To avoid this race simply hold the internal XArray lock when
incrementing the reference count, this ensures there cannot be a racing
call to xa_erase().
Security readout for executives and security teams
Plain-English summary
A local, low-privileged user may trigger a timing flaw in the Linux Panthor graphics driver while a group object is being removed. The resulting object-lifetime error could compromise confidentiality, integrity, or availability. Risk is limited to systems running affected kernels where the Panthor driver is present and reachable.
Executive priority
Treat as a high-priority kernel maintenance issue on systems using Panthor, especially shared or locally accessible hosts. It is not evidenced as an emergency internet-wide threat because exploitation requires local privileges and active exploitation is unconfirmed. Patch promptly through normal expedited kernel-update processes.
Technical view
CVE-2024-50174 is a CWE-362 race between retrieving a group pointer from an XArray and incrementing its reference count while another path may erase it. The fix holds the XArray lock during the reference-count increment. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, with high potential impact.
Likely exposure
Exposure is most likely on Linux systems using the drm/panthor driver and an affected kernel build. The supplied version data names 6.10, 6.10.14, 6.11.3, and 6.12, but its exact range boundaries are unclear. Confirm status through distribution advisories and backport records rather than version numbers alone.
Exploitation context
The supplied CVSS vector requires local access and low privileges; it does not describe a remote attack. The bundle marks the CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Practical exploitability beyond the documented race is therefore unconfirmed.
Researcher notes
The core issue is a pointer-lifetime race outside the XArray's structural protection: lookup and reference acquisition were not atomic relative to xa_erase(). The stable fix extends XArray locking across reference acquisition. The source bundle's flattened affected-version list is ambiguous, so commit ancestry and distribution backport evidence are stronger validation signals.
Mitigation direction
Install a vendor-supported kernel update containing the referenced stable fix or its documented backport.
Prioritize shared systems where untrusted local users can access the Panthor graphics driver.
If immediate updating is impossible, consult the Linux distribution or hardware vendor for supported interim guidance.
Validation and detection
Inventory running kernel builds and determine whether the Panthor driver is present and active.
Compare each build against distribution advisories and backport records for CVE-2024-50174.
Confirm the kernel changelog includes a referenced fix commit or an explicitly documented equivalent.
After updating and rebooting, verify the corrected kernel build is running.
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-362: 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.
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-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.