High 7.8Published Jul 19, 2026

CVE-2026-63809bpf: use kvfree() for replaced sysctl write buffer

Updated under an hour ago (Oct 26, 2026, 5:23 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: bpf: use kvfree() for replaced sysctl write buffer proc_sys_call_handler() allocates its temporary sysctl buffer with kvzalloc() and passes it to __cgroup_bpf_run_filter_sysctl(). Since kvzalloc() may fall back to vmalloc() for large allocations, freeing that buffer with kfree() is wrong and can corrupt memory. Use kvfree() to safely handle both kmalloc and kvzalloc()/vmalloc allocations. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc5. Reproduced the bug based on v7.1-rc4 in a QEMU x86_64 guest booted with KASAN and CONFIG_FAILSLAB enabled. To exercise the replacement path, the test tree also included the accompanying fix for the stale ret == 1 check in __cgroup_bpf_run_filter_sysctl(). The reproducer confines failslab injections to the proc_sys_call_handler() range, uses stacktrace-depth=32, and injects fail-nth=1 while writing 8191 bytes to /proc/sys/kernel/domainname from a task in the target cgroup. Under that setup, fail-nth=1 triggered the fault: BUG: unable to handle page fault for address: ffffeb0200024d48 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 SMP KASAN NOPTI CPU: 2 UID: 0 PID: 209 Comm: repro_proc_sys_ Not tainted 7.1.0-rc4-00686-g97625979a5d4 PREEMPT(lazy) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 RIP: 0010:kfree+0x6e/0x510 ... Call Trace: <TASK> ? __cgroup_bpf_run_filter_sysctl+0x626/0xc30 __cgroup_bpf_run_filter_sysctl+0x74d/0xc30 ? __pfx___cgroup_bpf_run_filter_sysctl+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? __kvmalloc_node_noprof+0x345/0x870 ? proc_sys_call_handler+0x250/0x480 ? srso_return_thunk+0x5/0x5f proc_sys_call_handler+0x3a2/0x480 ? __pfx_proc_sys_call_handler+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? selinux_file_permission+0x39f/0x500 ? srso_return_thunk+0x5/0x5f ? lock_is_held_type+0x9e/0x120 vfs_write+0x98e/0x1000 ... </TASK> With this fix applied on top of the same test setup, rerunning the reproducer with fail-nth=1 yields no corresponding Oops reports.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): CWE-787
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from b7925acd82926ebbf94a0f0783a3961f4e558856 before d0a81ed5ff5d0f9c3f63a4f9e5a4642c363ecd3e; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 77355ef7a9f6b0d2bdf65be3b37f2c1f365e20d2; from 4508943794efdd94171549c0bd52810e2f4ad9fe before e1d1e203a6000804c5d3b8a4aa4e52303c0c7ab2; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 81fc9a13acae99966232f0e055eb2e445263b89a; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 838fe9c28121777c59a9406710a68fcf77bb8017; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 65bd0c0afb0e1bf3287458e342429b069624f7d4; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 70df4de46577fab5e25418f014583155a147c902; 4508943794efdd94171549c0bd52810e2f4ad9fe builds before 4c21b5927d4364bfe7365f2700da5fea0ed0d004; and 3 more ranges	CNA record
linux linux_kernel linux:linux_kernel	from 5.10.20 before 5.10.260; from 5.11.3 before 5.15.211; from 5.16 before 6.1.177; from 6.2 before 6.6.144; from 6.7 before 6.12.95; from 6.13 before 6.18.38; from 6.19 before 7.1.3	NVD

References

https://git.kernel.org/stable/c/d0a81ed5ff5d0f9c3f63a4f9e5a4642c363ecd3epatch
https://git.kernel.org/stable/c/77355ef7a9f6b0d2bdf65be3b37f2c1f365e20d2patch
https://git.kernel.org/stable/c/e1d1e203a6000804c5d3b8a4aa4e52303c0c7ab2patch
https://git.kernel.org/stable/c/81fc9a13acae99966232f0e055eb2e445263b89apatch
https://git.kernel.org/stable/c/838fe9c28121777c59a9406710a68fcf77bb8017patch
https://git.kernel.org/stable/c/65bd0c0afb0e1bf3287458e342429b069624f7d4patch
https://git.kernel.org/stable/c/70df4de46577fab5e25418f014583155a147c902patch
https://git.kernel.org/stable/c/4c21b5927d4364bfe7365f2700da5fea0ed0d004patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.