tipc: avoid use-after-free in poll trace queue dumps
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b4b9771bcbbd5839b0f77aba55e2f85989ed6779 · < bed792737b5f1ba773054dbe984502958bdfe6ce| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's TIPC poll trace path can dump socket queues without holding the locks used by other queue-dump paths. If another context dequeues and frees an skb during the dump, the trace helper can dereference a stale queue entry. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with TIPC should check their versions; affected versions are not specified.