CVE-2025-21911: drm/imagination: avoid deadlock on fence release
In the Linux kernel, the following vulnerability has been resolved:
drm/imagination: avoid deadlock on fence release
Do scheduler queue fence release processing on a workqueue, rather
than in the release function itself.
Fixes deadlock issues such as the following:
[ 607.400437] ============================================
[ 607.405755] WARNING: possible recursive locking detected
[ 607.415500] --------------------------------------------
[ 607.420817] weston:zfq0/24149 is trying to acquire lock:
[ 607.426131] ffff000017d041a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: pvr_gem_object_vunmap+0x40/0xc0 [powervr]
[ 607.436728]
but task is already holding lock:
[ 607.442554] ffff000017d105a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: dma_buf_ioctl+0x250/0x554
[ 607.451727]
other info that might help us debug this:
[ 607.458245] Possible unsafe locking scenario:
[ 607.464155] CPU0
[ 607.466601] ----
[ 607.469044] lock(reservation_ww_class_mutex);
[ 607.473584] lock(reservation_ww_class_mutex);
[ 607.478114]
*** DEADLOCK ***
Security readout for executives and security teams
Plain-English summary
CVE-2025-21911 is a Linux kernel availability issue in the Imagination/PowerVR DRM graphics driver. A local user can trigger a locking deadlock during graphics fence release handling, potentially hanging affected graphics-related workloads or the system path involved. It is not described as exposing data or enabling code execution.
Executive priority
Treat as a targeted availability risk, not a broad remote compromise issue. Patch through normal kernel maintenance, faster for devices where graphics availability affects operations or customer service.
Technical view
The flaw is a CWE-667 improper locking issue in drm/imagination. Fence release processing ran inside the release function and could recursively acquire reservation locks, causing deadlock. The kernel fix moves scheduler queue fence release processing onto a workqueue.
Likely exposure
Exposure is most likely on Linux systems running affected kernels with the drm/imagination PowerVR graphics driver present or enabled. The CVE data identifies Linux kernel versions around 6.8 and later stable lines, but exact distribution exposure depends on backported fixes.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction, with high availability impact only. The provided sources do not report active exploitation, and CISA KEV status is false.
Researcher notes
Evidence supports a local denial-of-service class issue caused by lock recursion during fence release. Public data names stable kernel commits but does not provide exploit details or confirm exploitation in the wild.
Mitigation direction
Apply vendor Linux kernel updates containing the referenced stable fixes.
Prioritize systems using Imagination or PowerVR graphics hardware or drivers.
Confirm distribution kernels include the backported fix before marking remediated.
If patching is delayed, follow vendor guidance for reducing driver exposure.
Validation and detection
Inventory kernel versions and whether drm/imagination or powervr modules are present.
Check vendor changelogs for the referenced stable commit backports.
Review logs for recursive locking or deadlock warnings involving powervr or reservation locks.
Run normal graphics workload regression tests after kernel update.
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-667: 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.