What is CVE-2026-64075?

CVE-2026-64075 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, classified as a Use After Free flaw (CWE-416), affecting Linux kernel versions from 6.14 onward and patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64075 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

CVE-2026-64075 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-64075?

Yes, CVE-2026-64075 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64075 actively exploited?

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

What is Use After Free (CWE-416)?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/416.html

CVE-2026-64075

High

In the Linux kernel, the following vulnerability has been resolved: fprobe: Fix unregister_fprobe() to wait for RCU grace period Commit 4346ba1604093 ("fprobe: Rewrite fprobe on function-graph tracer") changed fprobe to register struct fprobe to an rcu-hlist, but it forgot to wait for RCU GP. Thus there can be use-after-free if the fprobe is released right after unregistering. This can be happened on fprobe event and sample module code. To fix this issue, add synchronize_rcu() in unregister_fprobe(). Note that BPF is OK because fprobe is used as a part of bpf_kprobe_multi_link. This unregisters its fprobe in bpf_kprobe_multi_link_release() and it is deallocated via bpf_kprobe_multi_link_dealloc(), which is invoked from bpf_link_defer_dealloc_rcu_gp() RCU callback. For BPF, this also introduced unregister_fprobe_async() which does NOT wait for RCU grace priod.

Package Linux Kernel

Published 2026-07-19

Last modified 2026-09-03

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-416

CVE-2026-64075 is a Use After Free vulnerability

What is Use After Free?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.14 and later are affected. Fixed in 6.18.34, 7.0.11, 7.1 and their respective stable series.

Affected from

≥ 6.14

Fixed in

✓ 6.18.34 6.18.x ✓ 7.0.11 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/56b4cfcf1518245493c60fd39c56978f508f1816

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

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

Patch

Details

CVE ID CVE-2026-64075

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-07-19

Modified 2026-09-03

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64075?

CVE-2026-64075 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 , classified as an Use After Free flaw (CWE-416) . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64075 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64075?

CVE-2026-64075 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-64075?

Yes. CVE-2026-64075 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64075 actively exploited?

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