CVE-2024-53087: drm/xe: Fix possible exec queue leak in exec IOCTL
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Fix possible exec queue leak in exec IOCTL
In a couple of places after an exec queue is looked up the exec IOCTL
returns on input errors without dropping the exec queue ref. Fix this
ensuring the exec queue ref is dropped on input error.
(cherry picked from commit 07064a200b40ac2195cb6b7b779897d9377e5e6f)
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can leak an execution-queue reference after invalid input to a DRM xe exec IOCTL. A local user or process could potentially consume kernel resources and cause denial of service. It is not described as exposing data or allowing code execution.
Executive priority
Treat this as a moderate availability risk. Patch through normal kernel maintenance, faster for shared workstations, GPU-enabled hosts, or multi-user Linux systems where local users could trigger resource exhaustion.
Technical view
CVE-2024-53087 is a CWE-401 resource-leak issue in Linux drm/xe. After an exec queue lookup, some input-error paths returned without dropping the exec queue reference. The fix ensures the reference is released on those error paths.
Likely exposure
Exposure is most likely on affected Linux kernels using the drm/xe driver and reachable local user or process access to the relevant DRM IOCTL. The bundle lists Linux kernel versions including 6.8, 6.11.8, and 6.12 as affected, but distro backports must be checked.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, and high availability impact. The source bundle does not identify active exploitation, public exploit availability, or CISA KEV listing.
Researcher notes
Evidence supports a local denial-of-service class resource leak in drm/xe exec IOCTL error handling. The bundle does not provide proof-of-concept details, exploit telemetry, or distribution-specific fixed versions, so validation should rely on kernel and vendor advisory mapping.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
Check vendor advisories for the exact fixed package version in your distribution.
Prioritize systems where local users or workloads can access drm/xe interfaces.
Restrict unnecessary local access to graphics/DRM devices where operationally feasible.
Validation and detection
Inventory Linux kernel versions across endpoints, workstations, and GPU-enabled systems.
Identify systems with drm/xe enabled or in use.
Compare installed kernel packages against vendor fixes for CVE-2024-53087.
Confirm change records reference the stable commits or CVE identifier.
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-401: 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-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.