CVE-2026-72299

Received Received - Intake

Heap-based Use-After-Free in Linux Kernel TIPC Networking

Publication date: 2026-08-15

Last updated on: 2026-08-23

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: restrict socket queue dumps in enqueue tracepoints tipc_sk_enqueue() runs with sk->sk_lock.slock held while the socket is owned by user context. The spinlock protects the backlog queue in this path, but it does not serialize against the socket owner consuming or purging sk_receive_queue. KASAN reported: CPU: 14 UID: 0 PID: 1050 Comm: tipc3 Not tainted 7.1.0-rc6+ #126 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x76/0xa0 lib/dump_stack.c:123 print_report+0xce/0x5b0 mm/kasan/report.c:482 kasan_report+0xc6/0x100 mm/kasan/report.c:597 __asan_report_load4_noabort+0x14/0x30 mm/kasan/report_generic.c:380 tipc_skb_dump+0x1327/0x16f0 net/tipc/trace.c:73 tipc_list_dump+0x208/0x2e0 net/tipc/trace.c:187 tipc_sk_dump+0xaf6/0xd60 net/tipc/socket.c:3996 trace_event_raw_event_tipc_sk_class+0x312/0x5a0 net/tipc/trace.h:188 tipc_sk_rcv+0xb1d/0x1d50 net/tipc/socket.c:2497 tipc_node_xmit+0x1c3/0x1440 net/tipc/node.c:1689 __tipc_sendmsg+0x97a/0x1440 net/tipc/socket.c:1512 tipc_sendmsg+0x52/0x80 net/tipc/socket.c:1400 sock_sendmsg+0x2f6/0x3e0 net/socket.c:825 splice_to_socket+0x7f9/0x1010 fs/splice.c:884 do_splice+0xe21/0x2330 fs/splice.c:936 __do_splice+0x153/0x260 fs/splice.c:1431 __x64_sys_splice+0x150/0x230 fs/splice.c:1616 x64_sys_call+0xeb5/0x2790 arch/x86/entry/syscall_64.c:41 do_syscall_64+0xf3/0x620 arch/x86/entry/syscall_64.c:63 entry_SYSCALL_64_after_hwframe+0x76/0x7e arch/x86/entry/entry_64.S:130 RIP: 0033:0x71624e8aafe2 Code: 08 0f 85 71 3a ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 66 2e 0f 1f 84 00 00 00 00 00 66 RSP: 002b:0000716157ffed68 EFLAGS: 00000246 ORIG_RAX: 0000000000000113 RAX: ffffffffffffffda RBX: 0000716157fff6c0 RCX: 000071624e8aafe2 RDX: 000000000000005f RSI: 0000000000000000 RDI: 0000000000000066 RBP: 0000716157ffed90 R08: 0000000000008000 R09: 0000000000000001 R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffff00 R13: 0000000000000021 R14: 0000000000000000 R15: 00007fff89799c40 </TASK> The TIPC_DUMP_ALL tracepoints in tipc_sk_enqueue() also dump sk_receive_queue and can therefore dereference skbs that the socket owner has already dequeued or freed. Restrict these dumps to TIPC_DUMP_SK_BKLGQ, which matches the queue protected by the held spinlock. Keep the change limited to the enqueue path, where the unsafe queue dump is reachable while the socket is owned by user context.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-23

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-72299

EUVD

EUVD-2026-59198

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1.0-rc6+

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a Linux kernel vulnerability in the TIPC (Transparent Inter-Process Communication) module. The issue occurs in tipc_sk_enqueue() where a spinlock protects the backlog queue but does not prevent the socket owner from consuming or purging the receive queue. TIPC_DUMP_ALL tracepoints can dereference skbs (socket buffers) that have already been dequeued or freed by the socket owner, leading to a use-after-free or memory corruption.

Detection Guidance

This vulnerability is specific to the Linux kernel's TIPC module and requires kernel-level detection. Check if TIPC is enabled with 'lsmod | grep tipc'. Monitor kernel logs for KASAN reports or crashes involving tipc_sk_enqueue. Review tracepoint usage in TIPC with 'cat /sys/kernel/debug/tracing/available_filter_functions | grep tipc'.

Impact Analysis

This vulnerability could allow an attacker with local access to trigger a use-after-free condition or memory corruption in the Linux kernel. This may lead to system crashes, privilege escalation, or arbitrary code execution, depending on the kernel configuration and system state.

Compliance Impact

This vulnerability in the Linux kernel does not directly impact compliance with standards like GDPR or HIPAA. It is a local denial-of-service issue in the TIPC protocol that could allow a local attacker to crash the system by triggering a KASAN report. Compliance risks would only arise if exploitation led to unauthorized data access or service disruption, which is not indicated by the provided details.

Mitigation Strategies

Disable the TIPC module if not needed with 'sudo modprobe -r tipc'. If TIPC is required, update to a patched kernel version that includes the fix for this issue. Monitor vendor advisories for kernel updates addressing CVE-2026-72299.

Hi! I’m here to help you understand CVE-2026-72299. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70