CVE-2026-64371

What the bug is

Fix the easy cases where procfs currently calls ptrace_may_access() without exec_update_lock protection, where the fix is to simply add the extra lock or use mm_access(): - do_task_stat(): grab exec_update_lock - proc_pid_wchan(): grab exec_update_lock - proc_map_files_lookup(): use mm_access() instead of get_task_mm() - proc_map_files_readdir(): use mm_access() instead of get_task_mm() - proc_ns_get_link(): grab exec_update_lock - proc_ns_readlink(): grab exec_update_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/proc/array.c
fs/proc/base.c
fs/proc/namespaces.c

What this is

PROC FILESYSTEMMAINTAINERS section matched on fs/proc/ · linux-kernel@vger.kernel.org · Maintained

Check it on the machine

grep -w CONFIG_PROC_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.

Show whether Debian builds this, per release

Debian builds this code. Every release below compiles the affected file into the kernels it ships.

• bookworm, trixie, forky, sid, bookworm · linux-6.12y

y

built into the kernel image on every flavour - only a patch removes it

Build switch

CONFIG_PROC_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-07-25 (3 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/proc

Upstream fixes

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

Introduced	Fixed in	Commit
2.6.30	5.10.261	ae1e630bcaac
2.6.30	5.15.212	d54f14655fd7
2.6.30	6.1.178	bb43679356f1
2.6.30	6.6.145	7456ae990a97
2.6.30	6.12.97	4bfe8c481846
2.6.30	6.18.40	f9b4b03ccc9c
2.6.30	7.1.4	c1cfd63326f5
2.6.30	7.2	6650527444da
2.6.27.23	0	0
2.6.29.3	0	0

Debian advisories