tipc: avoid use-after-free in poll trace queue dumps
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d7940bb6a8e7ab28f972c2875cb05783216312dc, Kernel 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8, Kernel 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <d7940bb6a8e7ab28f972c2875cb05783216312dc, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <78706367fe1b98aee0a6de27c62b7f1e3035f38d, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <ac2f787980fdf4364cd5651a4c8128e59b8de3aa, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <ae7fc824970888b4fdaa076819c9a6f2fcede275, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <b4f1719dfea023220e0e6bd892b087d76b2a6a49, >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <bed792737b5f1ba773054dbe984502958bdfe6ce, =5.0 | d7940bb6a8e7ab28f972c2875cb05783216312dc, 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8, 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d, 78706367fe1b98aee0a6de27c62b7f1e3035f38d, ac2f787980fdf4364cd5651a4c8128e59b8de3aa, ae7fc824970888b4fdaa076819c9a6f2fcede275, b4f1719dfea023220e0e6bd892b087d76b2a6a49, bed792737b5f1ba773054dbe984502958bdfe6ce |
| linux-kernel: Kernel | >=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.44, >=6.19.0 <7.1.8, >=6.2.0 <6.6.151, >=6.7.0 <6.12.103, >=5.0.0 <5.10.265 | 5.15.216, 6.1.183, 6.18.44, 7.1.8, 6.6.151, 6.12.103, 5.10.265 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket