What is the CVSS score of CVE-2026-64129?

CVE-2026-64129 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2026-64129?

Yes, a patch is available for CVE-2026-64129. Update the affected software to the latest version immediately.

Linux Kernel CVE-2026-64129

EUVD-2026-45814 MEDIUM

Memory Leak (CWE-401)

2026-07-19 Linux

GHSA-536v-q9w2-w76r

Information Disclosure Linux Red Hat Suse

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

vuln.today AI

4.7 MEDIUM

Triggering the vulnerable migration error path requires device huge page workloads and a specific failure condition, warranting AC:H over the NVD's AC:L.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

SUSE

MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 13, 2026 - 15:29 vuln.today

CVSS changed

Aug 13, 2026 - 15:22 NVD

5.5 (MEDIUM)

Patch available

Jul 19, 2026 - 17:03 EUVD

CVE Published

Jul 19, 2026 - 15:40 nvd

MEDIUM 5.5

CVE Published

Jul 19, 2026 - 15:40 cve.org

UNKNOWN (no severity yet)

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

mm/migrate_device: fix spinlock leak in migrate_vma_insert_huge_pmd_page

When check_stable_address_space() fails after the PMD spinlock has been acquired via pmd_lock(), the code jumps directly to the abort label, bypassing the spin_unlock() call in unlock_abort. This causes the PMD spinlock to be permanently held, leading to a deadlock.

Change the goto target from abort to unlock_abort to ensure the spinlock is always released on this error path.

AnalysisAI

Spinlock leak in the Linux kernel's huge page device migration subsystem causes a local denial of service via deadlock. A low-privileged local user who can trigger the migrate_vma_insert_huge_pmd_page code path while inducing check_stable_address_space() to fail will leave the PMD spinlock permanently held, deadlocking any subsequent thread that attempts to acquire it. No public exploit has been identified and EPSS at 0.17% (7th percentile) reflects negligible real-world exploitation probability; the vulnerability is not in CISA KEV.

Technical ContextAI

The flaw resides in mm/migrate_device.c within the Linux kernel's device-assisted memory migration subsystem, which handles huge PMD (Page Middle Directory) page migration for heterogeneous memory environments such as GPU or NUMA device memory. The function migrate_vma_insert_huge_pmd_page acquires a PMD spinlock via pmd_lock(), but when check_stable_address_space() subsequently fails, the error path performs a goto abort rather than goto unlock_abort, bypassing the spin_unlock() call. This is classified under CWE-401 (Missing Release of Resource after Effective Lifetime) - the spinlock is the resource not released - which causes permanent lock contention and a kernel deadlock. CPE cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* covers all Linux kernel builds incorporating the vulnerable commit range introduced at a30b48bf1b244f11bf9b6d20cdccfe0c2264130c.

RemediationAI

Update the Linux kernel to a patched release: Linux 7.0.11, Linux 7.1, or Linux 6.19, which include the one-line goto fix (abort → unlock_abort) confirmed via upstream stable commits c715f7ccf7a294c058667b678a4ba50fad933c62 and 63451de16e0a08be40f9ab5e7c5c8f5c79676fb1. Ubuntu users should apply USN-8593-1 (https://ubuntu.com/security/notices/USN-8593-1). As a compensating control on systems where device huge page migration is not operationally required, disabling Transparent Huge Pages via 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' reduces the probability of hitting the vulnerable code path; note this may degrade throughput for memory-intensive workloads relying on THP. Alternatively, restricting local user access to device memory migration interfaces (e.g., via cgroup or seccomp policy) limits which users can trigger the path, with the trade-off of reduced GPU/accelerator memory management flexibility.

Same weakness CWE-401 – Memory Leak

View all

CVE-2020-13934 HIGH

7.5

CVE-2016-4232 HIGH POC

7.5

CVE-2024-25450 HIGH POC

8.8

CVE-2023-33718 HIGH POC

8.8

CVE-2019-6128 HIGH POC

8.8

CVE-2026-67183 HIGH POC

8.7

CVE-2023-34451 HIGH POC

8.2

CVE-2023-41484 HIGH POC

8.1

Same technique Information Disclosure

View all

CVE-2019-2725 CRITICAL POC

9.8

CVE-2021-34523 CRITICAL POC

9.0

CVE-2013-2251 CRITICAL POC

9.8

CVE-2017-5638 CRITICAL POC

9.8

CVE-2025-24813 CRITICAL POC

9.8

CVE-2015-1701 HIGH POC

7.8

CVE-2017-0147 HIGH POC

7.5

CVE-2014-6324 HIGH POC

8.8

Vendor StatusVendor

SUSE

Severity: Moderate

Product	Status
SUSE Linux Enterprise Desktop 15 SP7	Not-Affected
SUSE Linux Enterprise Desktop 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0	Not-Affected

CVE-2026-64129 vulnerability details – vuln.today

Back

Linux Kernel CVE-2026-64129

Severity by source

CVSS VectorNVD

Lifecycle Timeline

DescriptionNVD

AnalysisAI

Technical ContextAI

RemediationAI

Same weakness CWE-401 – Memory Leak

Same technique Information Disclosure

Vendor StatusVendor

SUSE

Share

External POC / Exploit Code