CVE-2026-64129: mm/migrate_device: fix spinlock leak in migrate_vma_insert_huge_pmd_page
In the Linux kernel, the following vulnerability has been resolved:
mm/migratedevice: fix spinlock leak in migratevmainserthugepmdpage
When checkstableaddressspace() fails after the PMD spinlock has been acquired via pmdlock(), the code jumps directly to the abort label, bypassing the spinunlock() call in unlockabort. This causes the PMD spinlock to be permanently held, leading to a deadlock.
Change the goto target from abort to unlockabort to ensure the spinlock is always released on this error path.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In mm/migrate_device, when check_stable_address_space() fails after acquiring the PMD spinlock via pmd_lock(), change the code path to jump to the unlock_abort label (instead of abort) so the spin_unlock() call in unlock_abort is executed and the PMD spinlock is not permanently held.
Linux kernel (mm/migrate_device) goto target for spinlock error path = unlock_abort
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64129?
The severity of CVE-2026-64129 is rated at 43 on the risk scale.
How do I fix CVE-2026-64129?
To fix CVE-2026-64129, ensure you update to the latest version of the Linux kernel where this vulnerability has been addressed.
What component is affected by CVE-2026-64129?
CVE-2026-64129 affects the memory management subsystem in the Linux kernel.
What type of vulnerability is CVE-2026-64129?
CVE-2026-64129 is categorized as a spinlock leak in the memory management functionality of the Linux kernel.
Is CVE-2026-64129 actively exploited?
At this time, there are no known active exploits reported for CVE-2026-64129.