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

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

CVE-2026-53167

fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios

EPSS 0.1%

Published 2026-06-25 (4 months ago) by the Linux kernel CNA. Subsystem fs/fuse. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-53167 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 12bookwormfixedDLA-4688-1 · 2026-07-18 · text6.1.177-1Update the kernel and reboot. DLA-4688-1 shipped the fix on 2026-07-18, in 6.1.177-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixedDSA-6381-1 · 2026-07-05 · text6.12.95-1Update the kernel and reboot. DSA-6381-1 shipped the fix on 2026-07-05, in 6.12.95-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.0.13-1Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.0.13-1Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

FUSE_NOTIFY_RETRIEVE must be limited to uptodate folios; !uptodate folios can contain uninitialized data. Since FUSE_NOTIFY_RETRIEVE is intended to only return data that is already in the page cache and not wait for data from the FUSE daemon, treat !uptodate folios as if they weren't present. This only has security impact on systems that don't enable automatic zero-initialization of all page allocations via CONFIG_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=1.

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/fuse/dev.c

What this is
FUSE FILESYSTEM [CORE]MAINTAINERS section matched on fs/fuse/ · fuse-devel@lists.linux.dev · Supported
Kernel module
fuse

Check it on the machine

grep -w CONFIG_FUSE_FS /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 fuse

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 code. Every release below compiles the affected file into the kernels it ships.

  • bookwormm
  • trixie, forky, sidy
m
a loadable module on every flavour - check lsmod, can be blacklisted
y
built into the kernel image on every flavour - only a patch removes it
Build switch
CONFIG_FUSE_FS

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-06-25 (4 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.13%, higher than 2.2% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
fs/fuse

Upstream fixes

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

IntroducedFixed inCommit
2.6.365.10.260feafe8ccb158
2.6.365.15.211651801d75ad0
2.6.366.1.1774e14f29473ed
2.6.366.6.1448bef2f840b43
2.6.366.12.9568a9282d5ea5
2.6.366.18.3656763afa0134
2.6.367.0.131fb8735a3a4d
2.6.367.14e3d1b2c48ca

Debian advisories

AdvisoryDateShipped toDebian
DLA-4717-12026-08-05bullseye 5.10.262-1tracker
DLA-4700-12026-07-26bullseye 6.1.177-1~deb11u1tracker
DLA-4688-12026-07-18bookworm 6.1.177-1tracker
DSA-6381-12026-07-05trixie 6.12.95-1tracker

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-53167, 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.