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

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

CVE-2026-98843

netfs: zero gaps in read-gaps folio to avoid writing back stale data

Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem fs/netfs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-98843 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.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

netfs_read_gaps() leaves gaps around a streaming write's dirty region unread on the server side, so a short/EOF response there left stale folio content that later got written back. Zero it after the read completes, not before: netfs_wait_for_read() returns rreq->transferred once ret >= 0, so build an iterator over the same bvec array the read used, advance past ret, and zero the rest. The dirty region already maps to sink pages in that array rather than the real folio, so this can't touch it, and only the actual shortfall gets zeroed instead of the whole gap upfront.

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

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-10-18 (today)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
not scored
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.126.18.56512eaf01ffab
6.127.2.102a62fe628a87
6.127.38db55c5cd831

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98843, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.