Skip to main content

Linux Kernel EUVDEUVD-2026-53269

| CVE-2026-64575 HIGH
2026-08-05 Linux GHSA-f2rf-qgfg-8rxx
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Local vector confirmed; AC raised to H because triggering GFP_ATOMIC realloc failure requires controlled memory pressure, making reliable exploitation non-trivial; PR:L retained as low-privilege shell plus capability is sufficient.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
4.4 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 08, 2026 - 15:29 vuln.today
CVSS changed
Aug 08, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Aug 05, 2026 - 09:01 EUVD
CVE Published
Aug 05, 2026 - 08:09 cve.org
HIGH 7.8
CVE Published
Aug 05, 2026 - 08:09 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

bpf: tcp: fix double sock release on batch realloc

bpf_iter_tcp_batch() releases the current batch via bpf_iter_tcp_put_batch(), which drops the socket refs and rewrites each slot with the socket cookie, then grows the batch. cur_sk/end_sk are kept for bpf_iter_tcp_resume(), but on realloc failure the function returns ERR_PTR() before resume runs, leaving cur_sk < end_sk over slots that now hold cookies rather than sock pointers. bpf_iter_tcp_seq_stop() then calls bpf_iter_tcp_put_batch() again and dereferences a cookie as a struct sock.

Empty the batch on the failure path so stop() does not release it again. The sockets were already freed by the first bpf_iter_tcp_put_batch(), so nothing leaks, and a later read() rescans the bucket from the start instead of skipping it. The sibling GFP_NOWAIT failure path still holds real socket references and is left for stop() to release.

BUG: KASAN: null-ptr-deref in __sock_gen_cookie Read of size 8 at addr 0000000000000059 by task exploit ... __sock_gen_cookie (net/core/sock_diag.c:28) bpf_iter_tcp_put_batch (net/ipv4/tcp_ipv4.c:2918) bpf_iter_tcp_seq_stop (net/ipv4/tcp_ipv4.c:3270) bpf_seq_read (kernel/bpf/bpf_iter.c:205) vfs_read (fs/read_write.c:572) ksys_read (fs/read_write.c:716) do_syscall_64 entry_SYSCALL_64_after_hwframe Kernel panic - not syncing: Fatal exception

AnalysisAI

Double-release memory corruption in the Linux kernel's BPF TCP iterator (bpf_iter_tcp_batch) allows a local low-privileged user with BPF iterator access to trigger a kernel panic. When batch reallocation fails, the first bpf_iter_tcp_put_batch() call frees socket references and overwrites batch slots with socket cookies; if realloc then fails, the iterator's stop routine executes a second put_batch() and dereferences those cookie integer values as struct sock pointers, causing a KASAN-detected null-pointer dereference and kernel panic. No public exploit identified at time of analysis; EPSS is 0.15% (5th percentile), indicating low current automated exploitation probability.

Technical ContextAI

The vulnerability resides in the Linux kernel's BPF TCP iterator subsystem, specifically bpf_iter_tcp_batch() in net/ipv4/tcp_ipv4.c. The BPF iterator framework allows userspace to iterate kernel data structures (here, TCP sockets) via read() on a BPF iterator file descriptor. The batch mechanism holds references to live struct sock objects. The bug is a classic use-after-free / double-free pattern: bpf_iter_tcp_put_batch() drops socket references and rewrites each batch slot with the socket's cookie (a plain integer), then bpf_iter_tcp_batch() attempts to grow the batch allocation. On GFP_ATOMIC realloc failure, the function returns ERR_PTR() immediately, leaving the iterator state with cur_sk < end_sk pointing to slots that now contain cookie integers. bpf_iter_tcp_seq_stop() subsequently calls bpf_iter_tcp_put_batch() again, which passes those integer cookie values to __sock_gen_cookie() as if they were struct sock pointers - dereferencing address 0x59 (the cookie value), causing the kernel panic. The KASAN trace confirms the null-ptr-deref at net/core/sock_diag.c:28. No formal CWE is assigned, but this maps to CWE-415 (Double Free) with a use-after-free impact pattern. Affected CPEs: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*.

RemediationAI

Upgrade to Linux kernel 6.18.42 or 7.1.6 for stable-branch users, or apply 7.2-rc5 if tracking the mainline development branch. The upstream fix empties the batch array on the GFP_ATOMIC realloc failure path so that bpf_iter_tcp_seq_stop() does not attempt a second release of already-freed slots; the GFP_NOWAIT failure path is correctly left for stop() to handle as it still holds live socket references. Patch commits are available directly at kernel.org/stable (see references above). If immediate kernel upgrade is not possible, a compensating control is to restrict access to BPF iterator functionality by revoking or not granting CAP_BPF and CAP_NET_ADMIN to unprivileged users and containers - this prevents non-root users from creating the TCP iterator file descriptor needed to trigger the path. Additionally, setting kernel.unprivileged_bpf_disabled=1 via sysctl blocks unprivileged BPF program loading on kernels that support it, reducing the attack surface. Note that disabling BPF capabilities may impact observability tooling (e.g., bpftrace, eBPF-based monitoring agents) running on the host.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-53269 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy