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().
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-63809 is a memory corruption vulnerability in the Linux kernel's BPF (Berkeley Packet Filter) subsystem that affects sysctl write buffer management. The vulnerability occurs when proc_sys_call_handler() allocates a temporary buffer using kvzalloc()—which can fall back to vmalloc() for large allocations—but then incorrectly frees it with kfree() instead of kvfree(). This mismatch between allocation and deallocation methods can corrupt kernel memory, potentially leading to privilege escalation, denial of service, or system crashes. Any system running a vulnerable Linux kernel version with BPF capabilities enabled is affected, particularly those handling large sysctl writes or running containerized workloads that utilize cgroup BPF filtering.
While Casky.ai currently shows zero matching skills for this specific CVE, practitioners using the platform would benefit from extended reasoning analysis around memory management vulnerabilities and kernel exploitation patterns. Security teams should monitor for detection patterns associated with abnormal kernel memory access (T1040 - Traffic Capture), suspicious sysctl modifications (T1548 - Abuse Elevation Control Mechanism), and cgroup-based container escapes (T1611 - Escape to Host). When analyzing this vulnerability, Casky's Claude-powered engine could identify related attack chains by examining kernel hardening bypass techniques and memory corruption exploitation methods, helping practitioners understand how this bug might be weaponized in real-world scenarios and prioritize patching strategies based on their environment's BPF usage patterns.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-63809. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation