data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-64067 in the interactive tracker

CVE-2026-64067

netfs: Fix missing barriers when accessing stream->subrequests locklessly

9.8 EPSS 0.5% AV:N

Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem fs/netfs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-64067 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed7.0.12-1Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.0.12-1Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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).

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/netfs/buffered_read.c
fs/netfs/misc.c
fs/netfs/read_collect.c
fs/netfs/write_collect.c
fs/netfs/write_issue.c
include/linux/list.h

What this is
FILESYSTEMS [NETFS LIBRARY]MAINTAINERS section matched on fs/netfs/ · netfs@lists.linux.dev · Supported
Kernel module
netfs

Check it on the machine

grep -w CONFIG_NETFS_SUPPORT /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w netfs

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.

  • bookworm, trixie, forky, sidm
m
a loadable module on every flavour - check lsmod, can be blacklisted
Build switch
CONFIG_NETFS_SUPPORT

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-07-19 (3 months ago)source
CVSS
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
network (AV:N)source
EPSS
0.50%, higher than 41.6% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
fs/netfs

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.106.18.57f048f297d93f
6.107.0.11293a4532c36f
6.107.1b5782e2d462c

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:NAttack vector, network
The bug is in the netfs client library used by CIFS/SMB, Ceph, 9p, AFS, and NFS clients; a remote file server controls when read/write completions arrive over the network and can time responses to hit the lockless subrequest list race during collection.
AC:LAttack complexity, low
The attacker controls both sides of the concurrency (issuing concurrent reads/writes and timing remote completions); on weakly-ordered architectures the missing barriers can cause deterministic misordering without relying on rare external conditions.
PR:NPrivileges required, none
A malicious or compromised remote SMB/Ceph/NFS server needs no local privileges on the victim; exploitation only requires the victim system to perform I/O against an already-mounted network filesystem share.
UI:NUser interaction, none
On servers and enterprise systems with persistent fstab/autofs mounts, automated processes (writeback, readahead, backup daemons) trigger netfs I/O without live end-user action at exploit time.
S:UScope, unchanged
Impact is kernel memory corruption and privilege escalation within the same kernel security boundary; this is not a VM escape or cross-authority boundary bypass.
C:HConfidentiality impact, high
Premature removal and freeing of in-flight subrequests is a use-after-free; the collector may read freed `netfs_io_subrequest` memory and stale counters, enabling arbitrary kernel memory disclosure.
I:HIntegrity impact, high
The UAF and concurrent access to subrequest fields while I/O handlers still run can corrupt heap metadata and subrequest state, providing a path to arbitrary kernel writes or code execution.
A:HAvailability impact, high
Freeing active subrequests while SMB/Ceph completion handlers still reference them can cause kernel oops, BUG, or panic from use-after-free and list corruption.