PatchSiren cyber security CVE debrief
CVE-2026-64100 Linux CVE debrief
A deadlock vulnerability was found in the Linux kernel's drm/msm component. The vulnerability occurs when kswapd0 holding fs_reclaim calls the MSM shrinker, which calls dma_resv_lock, acquiring fs_reclaim and resulting in a deadlock. The issue is resolved by using dma_resv_trylock() instead. This change prevents the deadlock by avoiding the acquisition of fs_reclaim while holding reservation_ww_class_acquire. Linux kernel developers and maintainers should review and apply the patch provided by the Linux kernel maintainers.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-19
- Original CVE updated
- 2026-08-11
- Advisory published
- 2026-07-19
- Advisory updated
- 2026-08-11
Who should care
Linux kernel developers and maintainers, users of Linux kernel versions affected by this vulnerability, and security teams responsible for patching and vulnerability management should review and apply the patch provided by the Linux kernel maintainers. They should also monitor systems for potential exploitation attempts and verify the effectiveness of the fix.
Technical summary
The Linux kernel's drm/msm component has a deadlock vulnerability. When kswapd0 holding fs_reclaim calls the MSM shrinker, it calls dma_resv_lock, which acquires fs_reclaim, resulting in a deadlock. The fix replaces dma_resv_lock with dma_resv_trylock(), dropping the unused wait-wound lock 'ticket'. This change prevents the deadlock by avoiding the acquisition of fs_reclaim while holding reservation_ww_class_acquire. The patch provided by the Linux kernel maintainers should be reviewed and applied to affected systems.
Defensive priority
High priority for Linux kernel developers and maintainers to patch the vulnerability.
Recommended defensive actions
- Review and apply the patch provided by the Linux kernel maintainers.
- Update Linux kernel versions to include the fix.
- Monitor systems for potential exploitation attempts.
- Verify the effectiveness of the fix.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
Evidence notes
The vulnerability was resolved by using dma_resv_trylock() instead of dma_resv_lock. The fix was applied to the Linux kernel. This change prevents the deadlock by avoiding the acquisition of fs_reclaim while holding reservation_ww_class_acquire. Linux kernel developers and maintainers should verify the patch and apply it to affected systems. Evidence limits suggest that the fix is effective, but further verification is needed to confirm that it does not introduce new issues.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64100 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64100
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64100 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64100
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3392291fc509d8ad6e4ad90f15b0a193f721cbc9
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/928788566c79046f71a211fc32c115400be76402
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/942968260e61d4a5d7552b20814b6277f9c553df
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.