What is CVE-2026-64067?

CVE-2026-64067 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10, affecting Linux kernel versions from 6.10 onward and patched in 7.0.11 and 7.1. CVE-2026-64067 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

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

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

Is CVE-2026-64067 actively exploited?

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

CVE-2026-64067

Critical

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing barriers when accessing stream->subrequests locklessly The list of subrequests attached to stream->subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq->flags without taking a barrier after getting the subreq pointer from the list. Relatedly, the functions that build the list don't use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by: (1) Add a new list_add_tail_release() function that uses a release barrier to set the pointer to the new member of the list. (2) Add a new list_first_entry_or_null_acquire() function that uses an acquire barrier to read the pointer to the first member in a list (or return NULL). (3) Use list_add_tail_release() when adding a subreq to ->subrequests. (4) Use list_first_entry_or_null_acquire() when initially accessing the front of the list (when an item is removed, the pointer to the new front iterm is obtained under the same lock).

Package Linux Kernel

Published 2026-07-19

Last modified 2026-07-30

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.8

out of 10

Critical

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

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

Affected from

≥ 6.10

Fixed in

✓ 7.0.11 7.0.x ✓ 7.1

References

2 total

Details

CVE ID CVE-2026-64067

Severity Critical

CVSS score 9.8 / 10

CVSS version 3.1

Published 2026-07-19

Modified 2026-07-30

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64067?

CVE-2026-64067 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 6.10 onward and has been patched in 7.0.11 and 7.1. CVE-2026-64067 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64067?

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

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

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