In the Linux kernel, the following vulnerability has been resolved:
drm/sched: Fix fence reference count leak
The last_scheduled fence leaks when an entity is being killed and adding
the cleanup callback fails.
Decrement the reference count of prev when dma_fence_add_callback()
fails, ensuring proper balance.
[phasta: add git tag info for stable kernel]
Security readout for executives and security teams
Plain-English summary
CVE-2025-21995 is a Linux kernel denial-of-service issue in the DRM scheduler. A local authenticated user could trigger a fence reference count leak that may exhaust resources and affect availability. It is not described as data theft or privilege escalation.
Executive priority
Treat as a routine but real availability fix. It should be included in normal kernel patch cycles, with higher urgency for shared Linux systems or workstations where untrusted local users have access.
Technical view
The bug is in drm/sched cleanup handling. When an entity is killed and dma_fence_add_callback() fails, last_scheduled can leak because the previous fence reference is not decremented. The fix balances the reference count. CVSS is 5.5, local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions with DRM scheduler code. The CVE record lists Linux kernel versions including 6.2, 6.6.85, 6.12.21, 6.13.9, and 6.14 as affected markers. Distribution backports may change practical exposure.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked in KEV. The CVSS vector requires local access and low privileges. Available evidence supports availability risk, not remote compromise or confidentiality impact.
Researcher notes
The public record identifies a reference-count leak and stable kernel fixes, but does not provide a CWE, exploit evidence, or detailed distribution status. Avoid assuming exposure from upstream versions alone; validate against vendor kernels and backport notes.
Mitigation direction
Apply Linux kernel or distribution updates that include the referenced stable fixes.
Check vendor advisories for backported fixes before relying on upstream version numbers.
Prioritize multi-user Linux systems where local users can exercise GPU or DRM paths.
Monitor systems for unusual resource exhaustion until updates are deployed.
Validation and detection
Inventory running kernel versions across Linux hosts.
Confirm whether distribution kernels contain the referenced stable commits or equivalent backports.
Map exposed systems that allow local users access to DRM or GPU functionality.
Review vendor security advisories for CVE-2025-21995 remediation status.
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.
cve · low confidence lookup
CVE-2025-21995 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.