In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: fix spinlock leak in migrate_vma_insert_huge_pmd_page When… (CVE-2026-64129)
A vulnerability in the Linux kernel's memory management subsystem was fixed to address a spinlock leak in the migrate_vma_insert_huge_pmd_page function. The issue occurs when check_stable_address_space() fails after acquiring a PMD spinlock, causing the code to bypass the spin_unlock call and leading to a permanent lock and deadlock. The fix changes the error handling to ensure the spinlock is always released.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel involves a spinlock leak in the migrate_vma_insert_huge_pmd_page function within the memory management code. Specifically, if check_stable_address_space() fails after the PMD spinlock is acquired via pmd_lock(), the error path jumps directly to an abort label, skipping the spin_unlock call in unlock_abort. This results in the PMD spinlock remaining held indefinitely, causing a deadlock. The patch modifies the goto target from abort to unlock_abort to guarantee the spinlock is released on this error path.
Potential Impact
This vulnerability can cause a deadlock in the Linux kernel due to a spinlock being permanently held. While it does not impact confidentiality or integrity, it affects availability by potentially halting kernel operations that require the PMD spinlock. The CVSS score of 5.5 (medium severity) reflects this availability impact without privilege escalation or remote exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should monitor vendor communications for updates. No known exploits are reported in the wild at this time.
In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: fix spinlock leak in migrate_vma_insert_huge_pmd_page When… (CVE-2026-64129)
Description
A vulnerability in the Linux kernel's memory management subsystem was fixed to address a spinlock leak in the migrate_vma_insert_huge_pmd_page function. The issue occurs when check_stable_address_space() fails after acquiring a PMD spinlock, causing the code to bypass the spin_unlock call and leading to a permanent lock and deadlock. The fix changes the error handling to ensure the spinlock is always released.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel involves a spinlock leak in the migrate_vma_insert_huge_pmd_page function within the memory management code. Specifically, if check_stable_address_space() fails after the PMD spinlock is acquired via pmd_lock(), the error path jumps directly to an abort label, skipping the spin_unlock call in unlock_abort. This results in the PMD spinlock remaining held indefinitely, causing a deadlock. The patch modifies the goto target from abort to unlock_abort to guarantee the spinlock is released on this error path.
Potential Impact
This vulnerability can cause a deadlock in the Linux kernel due to a spinlock being permanently held. While it does not impact confidentiality or integrity, it affects availability by potentially halting kernel operations that require the PMD spinlock. The CVSS score of 5.5 (medium severity) reflects this availability impact without privilege escalation or remote exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should monitor vendor communications for updates. No known exploits are reported in the wild at this time.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-536v-q9w2-w76r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64129"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912b224
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 08/13/2026, 19:15:45 UTC
Last updated: 09/02/2026, 10:52:10 UTC
Views: 57
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.