What is CVE-2026-64377?

CVE-2026-64377 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.2 onward and patched in 6.12.96, 6.18.39, 7.1.4 and others. CVE-2026-64377 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64377?

CVE-2026-64377 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

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

Yes, CVE-2026-64377 has been patched. Fixed versions include 6.12.96, 6.18.39, 7.1.4 and others. If you are running Linux kernel 6.2 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64377 actively exploited?

CVE-2026-64377 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-64377

High

In the Linux kernel, the following vulnerability has been resolved: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.

Package Linux Kernel

Published 2026-07-25

Last modified 2026-09-08

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Weakness type

CWE-415

CVE-2026-64377 is classified as CWE-415

See CWE-415 on MITRE CWE for full details on this weakness type.

Affected versions

Linux kernel versions 6.2 and later are affected. Fixed in 6.12.96, 6.18.39, 7.1.4, 7.2 and their respective stable series.

Affected from

≥ 6.2

Fixed in

✓ 6.12.96 6.12.x ✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2

References

4 total

Kernel Git
https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13

Patch
Kernel Git
https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d

Patch
Kernel Git
https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2

Patch
Kernel Git
https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489

Patch

Details

CVE ID CVE-2026-64377

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-07-25

Modified 2026-09-08

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64377?

CVE-2026-64377 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.2 onward and has been patched in 6.12.96, 6.18.39, 7.1.4 and others. CVE-2026-64377 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64377?

CVE-2026-64377 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-64377?

Yes. CVE-2026-64377 has been patched. Fixed versions include 6.12.96, 6.18.39, 7.1.4 and others. If you are running Linux kernel 6.2 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64377 actively exploited?

No. CVE-2026-64377 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.