In certain Linux kernel builds the DRM MSM shrinker can acquire locks in a circular dependency that leads to a deadlock. When the kswapd task holds a file-system reclaim lock while invoking the MSM shrinker, the shrinker attempts to grab the same lock via the reservation work‑write lock, which again depends on the reclaim lock. The result is a kernel deadlock that is reported by the lockdep diagnostics and can bring the system to a halt. The flaw is a classic race condition (CWE‑833) and could render a device unusable as no services can continue after the kernel stalls, creating a denial scenario issue exists in any Linux kernel that bundles the DRM MSM subsystem, such as kernel releases targeting Snapdragon platforms. No specific version ranges were listed, so all kernel builds that contain the affected code path are potentially vulnerable.

All Linux kernel versions that include the DRM MSM subsystem used in Qualcomm Snapdragon mobile platforms are potentially impacted. This includes any distribution shipping the upstream kernel with that subsystem, regardless of the specific release number, because the vendor information lists Linux:Linux. Version details are not supplied, so the entire codebase containing the affected shrinker path is considered at risk.

A CVSS score is not supplied and the EPSS score is below 1 %, indicating that no large‑scale automated exploitation has been observed. The bug is not listed in the CISA KEV catalog. Exploitation would most likely require a malicious actor to trigger heavy memory‑pressure conditions on a device that runs the affected kernel, and it is not a remote‑attacker scenario. The low EPSS suggests that the likelihood of opportunistic exploitation is small, but the impact of a system‑wide deadlock means that any successful attack will be highly disruptive. The overall risk can be considered low to moderate, depending on the criticality of the affected device.