In the Linux kernel, the following vulnerability has been resolved: tipc: avoid use-after-free in poll trace queue dumps TIPC socket tracepoints dump queue state through tipc_sk_dump(). Most queue-dump callsites already serialize that walk under the socket lock or sk->sk_lock.slock, but tipc_poll() calls trace_tipc_sk_poll(..., TIPC_DUMP_ALL, ...) without holding either lock. That lets the poll trace path reach tipc_list_dump() and backlog head/tail dumping while another context dequeues and frees an skb, leaving the trace helper dereferencing a stale queue entry. Stop the unlocked poll trace site from requesting queue dumps. Other queue dump trace callsites keep their existing output under the locking they already provide, while poll still emits the event itself without walking live queue members from an unlocked context.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.8NVD modified 2026-10-16 20:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- https://git.kernel.org/stable/c/3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8
- https://git.kernel.org/stable/c/5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d
- https://git.kernel.org/stable/c/78706367fe1b98aee0a6de27c62b7f1e3035f38d
- https://git.kernel.org/stable/c/ac2f787980fdf4364cd5651a4c8128e59b8de3aa
- https://git.kernel.org/stable/c/ae7fc824970888b4fdaa076819c9a6f2fcede275
- https://git.kernel.org/stable/c/b4f1719dfea023220e0e6bd892b087d76b2a6a49
- https://git.kernel.org/stable/c/bed792737b5f1ba773054dbe984502958bdfe6ce
- https://git.kernel.org/stable/c/d7940bb6a8e7ab28f972c2875cb05783216312dc