CVE-2026-72299

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: 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 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

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 v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

tipc: restrict socket queue dumps in enqueue tracepoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b9e100815f4b55e9ccaf6af9a3aba173eb13d381
generic

tipc: restrict socket queue dumps in enqueue tracepoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/acd7df8d955480a6f6e5bb809da67b1500cc3cf4
generic

tipc: restrict socket queue dumps in enqueue tracepoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6acbbe54215d5f4251593000cff2bf51d6748713
generic

tipc: restrict socket queue dumps in enqueue tracepoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61a55fa24a5d737436018764a647fe5b6cb36371
generic

tipc: restrict socket queue dumps in enqueue tracepoints - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12876864f9de5fa6f611a30c6c17e405a773bf0a

Vendor Advisories for CVE-2026-72299(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 49× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:33 UTCGHSA enrichment
  2. 2026-08-21 02:34 UTCEG score recompute
  3. 2026-08-21 02:34 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:35 UTCGHSA enrichment
  6. 2026-08-20 18:37 UTCGHSA enrichment
  7. 2026-08-20 14:39 UTCGHSA enrichment
  8. 2026-08-20 10:41 UTCGHSA enrichment
  9. 2026-08-20 06:43 UTCGHSA enrichment
  10. 2026-08-20 02:44 UTCGHSA enrichment
  11. 2026-08-19 22:46 UTCGHSA enrichment
  12. 2026-08-19 18:48 UTCEG score recompute
  13. 2026-08-19 18:48 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:49 UTCGHSA enrichment
  16. 2026-08-19 10:51 UTCGHSA enrichment
  17. 2026-08-19 06:52 UTCGHSA enrichment
  18. 2026-08-19 02:54 UTCGHSA enrichment
  19. 2026-08-18 22:53 UTCGHSA enrichment
  20. 2026-08-18 18:56 UTCGHSA enrichment
  21. 2026-08-18 14:58 UTCEG score recompute
  22. 2026-08-18 14:58 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 10:55 UTCGHSA enrichment
Show 24 more
  1. 2026-08-18 06:56 UTCGHSA enrichment
  2. 2026-08-18 02:57 UTCGHSA enrichment
  3. 2026-08-17 22:59 UTCGHSA enrichment
  4. 2026-08-17 19:00 UTCGHSA enrichment
  5. 2026-08-17 14:15 UTCEG score recompute
  6. 2026-08-17 14:15 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:17 UTCEG score recompute
  9. 2026-08-17 10:17 UTCGHSA enrichment
  10. 2026-08-17 06:19 UTCEG score recompute
  11. 2026-08-17 06:19 UTCGHSA enrichment
  12. 2026-08-17 05:59 UTCEG score recompute 9.80
  13. 2026-08-17 05:59 UTCGHSA enrichment
  14. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  15. 2026-08-17 05:30 UTCEG score recompute
  16. 2026-08-17 05:30 UTCGHSA enrichment
  17. 2026-08-17 05:24 UTCMITRE cvelistV5
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 06:37 UTCGHSA enrichment
  22. 2026-08-15 06:23 UTCNVD update
  23. 2026-08-15 06:07 UTCEG score recompute
  24. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72299?
CVE-2026-72299 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: tipc: restrict socket queue dumps in enqueue tracepoints tipcskenqueue() 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…
When was CVE-2026-72299 disclosed?
CVE-2026-72299 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72299 actively exploited?
CVE-2026-72299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72299?
CVE-2026-72299 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72299, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72299

Explore →

Is Your Infrastructure Affected by CVE-2026-72299?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.