Skip to main content

Linux Kernel CVE-2026-72299

| EUVDEUVD-2026-59198 CRITICAL
2026-08-15 Linux GHSA-9rp6-pw5h-7mv9
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
3.0 LOW

Reachable only with local privileged access to enable TIPC debug tracepoints (PR:H) and by winning a queue race (AC:H); yields freed-memory read (C:L) and possible crash (A:L), no integrity impact.

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

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

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

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 08:16 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
9.8 (CRITICAL)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:55 cve.org
CRITICAL 9.8
CVE Published
Aug 15, 2026 - 05:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Out-of-bounds/use-after-free read in the Linux kernel TIPC subsystem occurs when the enqueue-path debug tracepoints in tipc_sk_enqueue() dump sk_receive_queue while only sk->sk_lock.slock is held. Because that spinlock protects only the backlog queue and does not serialize against the socket owner consuming or purging the receive queue, the tracepoint can dereference skbs already dequeued or freed, as caught by KASAN. There is no public exploit identified at time of analysis, EPSS is very low (0.21%, 11th percentile), and the issue is only reachable when TIPC debug tracepoints are active.

Technical ContextAI

TIPC (Transparent Inter-Process Communication) is a niche Linux kernel networking protocol used for cluster/intra-node messaging, typically compiled as the tipc module and not loaded by default. The defect lives in the kernel's ftrace/tracepoint instrumentation for TIPC sockets: tipc_sk_dump()/tipc_list_dump()/tipc_skb_dump() in net/tipc/trace.c walk socket queues to emit trace events. In the enqueue path (tipc_sk_rcv → tipc_sk_enqueue), the socket is owned by user context and only the backlog spinlock is held, so dumping sk_receive_queue (TIPC_DUMP_ALL) races with the owner draining or freeing that queue - a classic concurrent-access/use-after-free read of skb memory. CWE is unclassified in the source data, but the behavior maps to a use-after-free / out-of-bounds read (CWE-416/CWE-125). The fix restricts these enqueue-path dumps to TIPC_DUMP_SK_BKLGQ, the queue actually protected by the held spinlock.

RemediationAI

Vendor-released patch: update to a fixed stable kernel - 6.6.148, 6.12.101, 6.18.40, or 7.1.5 (fix also in 7.2-rc1) - via your distribution's kernel update channel, referencing the git.kernel.org stable commits listed in the CVE. Until patched, the exposure can be eliminated operationally: because the bug is only reachable through the TIPC enqueue-path debug tracepoints, disable those tracepoints (do not enable TIPC_DUMP_ALL / the tipc_sk_* trace events in tracefs) and restrict access to /sys/kernel/tracing and debugfs to root only; the trade-off is loss of TIPC tracing for debugging. If TIPC is not required, unload or blacklist the tipc module (modprobe -r tipc / blacklist tipc), which removes the code path entirely with no impact on systems that do not use TIPC clustering. Apply the vendor patch at https://nvd.nist.gov/vuln/detail/CVE-2026-72299.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-72299 vulnerability details – vuln.today

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