In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix shrinker deadlock With PROVE_LOCKING on an Snapdragon X1 and VM… (CVE-2026-64100)
A deadlock vulnerability in the Linux kernel's drm/msm driver was resolved. The issue occurs with PROVE_LOCKING enabled on Snapdragon X1 platforms under VM reclaim pressure, causing a circular locking dependency involving reservation locks and fs_reclaim locks. This deadlock can cause kernel tasks to hang during memory reclaim operations. The fix replaces a blocking lock acquisition with a trylock to prevent the deadlock scenario.
AI Analysis
Technical Summary
CVE-2026-64100 addresses a deadlock in the Linux kernel drm/msm driver related to the shrinker mechanism. Under certain conditions on Snapdragon X1 hardware with PROVE_LOCKING enabled, a circular locking dependency arises between reservation_ww_class_acquire, reservation_ww_class_mutex, and fs_reclaim locks. This deadlock manifests during VM reclaim pressure when kswapd0 holds fs_reclaim and attempts to acquire the MSM shrinker lock, which in turn tries to reacquire fs_reclaim, causing a circular wait. The patch changes the locking strategy by using dma_resv_trylock() instead of dma_resv_lock(), dropping the wait-wound lock ticket to break the deadlock chain.
Potential Impact
The vulnerability can cause kernel deadlocks during memory reclaim operations on affected hardware, potentially leading to system hangs or degraded performance. There is no indication of privilege escalation or code execution impact. The issue is specific to certain kernel configurations and hardware (Snapdragon X1 with PROVE_LOCKING).
Mitigation Recommendations
A fix has been implemented in the Linux kernel to resolve this deadlock by modifying the locking mechanism in the drm/msm driver. Users should apply the official kernel update or patch that includes this fix. Since this is a kernel-level issue, upgrading to a kernel version containing the patch is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed version and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix shrinker deadlock With PROVE_LOCKING on an Snapdragon X1 and VM… (CVE-2026-64100)
Description
A deadlock vulnerability in the Linux kernel's drm/msm driver was resolved. The issue occurs with PROVE_LOCKING enabled on Snapdragon X1 platforms under VM reclaim pressure, causing a circular locking dependency involving reservation locks and fs_reclaim locks. This deadlock can cause kernel tasks to hang during memory reclaim operations. The fix replaces a blocking lock acquisition with a trylock to prevent the deadlock scenario.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-64100 addresses a deadlock in the Linux kernel drm/msm driver related to the shrinker mechanism. Under certain conditions on Snapdragon X1 hardware with PROVE_LOCKING enabled, a circular locking dependency arises between reservation_ww_class_acquire, reservation_ww_class_mutex, and fs_reclaim locks. This deadlock manifests during VM reclaim pressure when kswapd0 holds fs_reclaim and attempts to acquire the MSM shrinker lock, which in turn tries to reacquire fs_reclaim, causing a circular wait. The patch changes the locking strategy by using dma_resv_trylock() instead of dma_resv_lock(), dropping the wait-wound lock ticket to break the deadlock chain.
Potential Impact
The vulnerability can cause kernel deadlocks during memory reclaim operations on affected hardware, potentially leading to system hangs or degraded performance. There is no indication of privilege escalation or code execution impact. The issue is specific to certain kernel configurations and hardware (Snapdragon X1 with PROVE_LOCKING).
Mitigation Recommendations
A fix has been implemented in the Linux kernel to resolve this deadlock by modifying the locking mechanism in the drm/msm driver. Users should apply the official kernel update or patch that includes this fix. Since this is a kernel-level issue, upgrading to a kernel version containing the patch is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed version and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3q3c-q46p-rwcg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64100"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912bbdf
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:50:12 UTC
Last updated: 07/20/2026, 18:24:32 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.