Linux
tipc: avoid use-after-free in poll trace queue dumps
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < ae7fc824970888b4fdaa076819c9a6f2fcede275
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < 78706367fe1b98aee0a6de27c62b7f1e3035f38d
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < d7940bb6a8e7ab28f972c2875cb05783216312dc
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < bed792737b5f1ba773054dbe984502958bdfe6ce
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < ac2f787980fdf4364cd5651a4c8128e59b8de3aa
- >= b4b9771bcbbd5839b0f77aba55e2f85989ed6779, < b4f1719dfea023220e0e6bd892b087d76b2a6a49
Fixed in 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8, ae7fc824970888b4fdaa076819c9a6f2fcede275, 78706367fe1b98aee0a6de27c62b7f1e3035f38d, d7940bb6a8e7ab28f972c2875cb05783216312dc, 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d, bed792737b5f1ba773054dbe984502958bdfe6ce, ac2f787980fdf4364cd5651a4c8128e59b8de3aa, b4f1719dfea023220e0e6bd892b087d76b2a6a49
- 5.0
Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2
Mitigation
Upgrade Linux to 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8 or ae7fc824970888b4fdaa076819c9a6f2fcede275 or 78706367fe1b98aee0a6de27c62b7f1e3035f38d or d7940bb6a8e7ab28f972c2875cb05783216312dc or 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d or bed792737b5f1ba773054dbe984502958bdfe6ce or ac2f787980fdf4364cd5651a4c8128e59b8de3aa or b4f1719dfea023220e0e6bd892b087d76b2a6a49 or later.
Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.151 or 6.12.103 or 6.18.44 or 7.1.8 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.