CVE & CISA-KEV Catalog

CVE-2026-63809

MEDIUM
5.5
CVSS v3
NVD

Description

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.

How to fix

Remediation Available
linuxDebian
Fixed in:6.1.177-1CVE-2026-63809
Fixed in:6.12.95-1CVE-2026-63809
Fixed in:7.1.3-1CVE-2026-63809
linuxUbuntu
Fixed in:5.15.0-198.208USN-8875-1
Fixed in:6.8.0-147.147USN-8917-1
linux-awsUbuntu
Fixed in:5.15.0-1117.124USN-8875-1
Fixed in:6.8.0-1067.70USN-8917-1
linux-aws-5.15Ubuntu
Fixed in:5.15.0-1117.124~20.04.1USN-8875-1
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1069.74~22.04.1USN-9024-1
linux-aws-7.0Ubuntu
Fixed in:7.0.0-1012.12~24.04.1USN-8726-1
linux-aws-fipsUbuntu
Fixed in:5.15.0-1117.124+fips1USN-8875-1
Fixed in:6.8.0-1067.70+fips1USN-8917-1
linux-azureUbuntu
Fixed in:5.15.0-1123.132USN-8875-1
Fixed in:6.8.0-1071.79USN-8918-1
linux-azure-5.15Ubuntu
Fixed in:5.15.0-1123.132~20.04.1USN-8875-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1073.82~22.04.1USN-9026-1
linux-azure-7.0Ubuntu
Fixed in:7.0.0-1014.14~24.04.1USN-8728-2
linux-azure-fdeUbuntu
Fixed in:6.8.0-1069.76USN-8918-1
linux-azure-fde-5.15Ubuntu
Fixed in:5.15.0-1122.131~20.04.1USN-8875-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1071.78~22.04.1USN-9026-1
linux-azure-fipsUbuntu
Fixed in:5.15.0-1123.132+fips1USN-8875-1
Fixed in:6.8.0-1071.79+fips1USN-8918-1
linux-fipsUbuntu
Fixed in:5.15.0-198.208+fips1USN-8875-1
Fixed in:6.8.0-147.147+fips1USN-8917-1
linux-gcpUbuntu
Fixed in:5.15.0-1118.128USN-8877-1
Fixed in:6.8.0-1071.79USN-8917-1
linux-gcp-5.15Ubuntu
Fixed in:5.15.0-1118.128~20.04.1USN-8878-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1073.81~22.04.1USN-9024-1
linux-gcp-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-gcp-fipsUbuntu
Fixed in:5.15.0-1118.128+fips1USN-8877-1
Fixed in:6.8.0-1071.79+fips1USN-8917-1
linux-gkeUbuntu
Fixed in:5.15.0-1113.119USN-8875-1
Fixed in:6.8.0-1066.74USN-8917-1
linux-gkeopUbuntu
Fixed in:5.15.0-1100.108USN-8875-1
Fixed in:6.8.0-1052.56USN-8917-1
linux-hwe-5.15Ubuntu
Fixed in:5.15.0-198.208~20.04.1USN-8875-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-149.149~22.04.1USN-9066-1
linux-hwe-7.0Ubuntu
Fixed in:7.0.0-31.31~24.04.1USN-8726-1
linux-ibmUbuntu
Fixed in:5.15.0-1111.115USN-8875-1
Fixed in:6.8.0-1067.68USN-8917-1
linux-ibm-5.15Ubuntu
Fixed in:5.15.0-1111.115~20.04.1USN-8875-1
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1069.70~22.04.1USN-9024-1
linux-image-5.15.0-1059-nvidia-tegra-igxUbuntu
Fixed in:5.15.0-1059.59USN-8963-1

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.15%probability of exploitation in 30 days
5thpercentile

Low risk: more likely to be exploited than 5% of all known CVEs.

References

Related Vulnerabilities

Other CWE-763 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2007-4367High9.38.7%-Fix
CVE-2015-2695Medium5.06.0%-Fix
CVE-2013-4695High7.85.3%--
CVE-2020-36224High7.54.4%-Fix
CVE-2022-31625High8.13.8%-Fix
CVE-2021-42377Critical9.83.6%-Fix

Common questions

How do I fix CVE-2026-63809?

Published advisories record a fix for 288 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-63809 being actively exploited?

Not that we know of. CVE-2026-63809 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 5% of all scored CVEs.

How severe is CVE-2026-63809?

CVE-2026-63809 has a CVSS v3 base score of 5.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-63809 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-5.15 (Ubuntu), and 284 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-63809
CVE-2026-63809 severity badge

Markdown

[![CVE-2026-63809](https://tridentstack.com/cve/badge/CVE-2026-63809.svg)](https://tridentstack.com/cve/CVE-2026-63809)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-63809"><img src="https://tridentstack.com/cve/badge/CVE-2026-63809.svg" alt="CVE-2026-63809"></a>

Check your Linux endpoints for this class of vulnerability

TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.

Patch your fleet freeStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-22.