net/x25: fix use-after-free in x25_kill_by_neigh()
Subsystems (4)
PATCH 1/1 net/x25: fix use-after-free in x25_kill_by_neigh()
x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped.
The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock.
Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid.
A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().
---
Trail of Bits has a reproducer that triggers kernel panic demonstrating the bug, and can share it if needed.
net/x25/af_x25.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
net/x25/af_x25.c +6 -2
@@ -1768,15 +1768,19 @@ void x25_kill_by_neigh(struct x25_neigh *nb) {struct sock *s; +again:write_lock_bh (&x25_list_lock);sk_for_each (s, &x25_list) {if (x25_sk (s)->neighbour == nb) { +sock_hold (s);write_unlock_bh (&x25_list_lock);lock_sock (s); -x25_disconnect (s,ENETUNREACH ,0 ,0 ); +if (x25_sk (s)->neighbour == nb) +x25_disconnect (s,ENETUNREACH ,0 ,0 );release_sock (s); -write_lock_bh (&x25_list_lock); +sock_put (s); + goto again; } }write_unlock_bh (&x25_list_lock);
Quoted 48 lines · David Lee
x25_kill_by_neigh()walks the global X.25 socket list looking for sockets attached to a terminating neighbour.x25_list_lockprotects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped.The function currently drops
x25_list_lockbefore callinglock_sock(s). A concurrent close can runx25_release(), remove the same socket fromx25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/structx25_sock.Take
sock_hold(s)whilex25_list_lockstill proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour afterlock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid.A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in
x25_kill_by_neigh().Fixes 7781607938c8 ("net/x25: Fix null-ptr-deref caused by x25_disconnect")Signed-off-by David Lee <[email protected]>Assisted-by Codex:gpt-5.5---
Trail of Bits has a reproducer that triggers kernel panic demonstrating the bug, and can share it if needed.
net/x25/af_x25.c| 8 ++++++--1 file changed, 6 insertions(+), 2 deletions(-)net/x25/af_x25.c +2
-0@@ -1768,15 +1768,19 @@ void x25_kill_by_neigh(struct x25_neigh *nb) {struct sock *s; +again:write_lock_bh (&x25_list_lock);sk_for_each (s, &x25_list) {if (x25_sk (s)->neighbour == nb) { +sock_hold (s);write_unlock_bh (&x25_list_lock);lock_sock (s);
net/x25/af_x25.c void x25_kill_by_neigh(struct x25_neigh *nb) · line 1786
Quoted 10 lines
net/x25/af_x25.c +4
-2-x25_disconnect (s,ENETUNREACH ,0 ,0 ); +if (x25_sk (s)->neighbour == nb) +x25_disconnect (s,ENETUNREACH ,0 ,0 );release_sock (s); -write_lock_bh (&x25_list_lock); +sock_put (s); + goto again; } }write_unlock_bh (&x25_list_lock);
LGTM, Thanks.
Paolo Abeni
maintainerQuoted 16 lines · David Lee
net/x25/af_x25.c +2
-0@@ -1768,15 +1768,19 @@ void x25_kill_by_neigh(struct x25_neigh *nb) {struct sock *s; +again:write_lock_bh (&x25_list_lock);sk_for_each (s, &x25_list) {if (x25_sk (s)->neighbour == nb) { +sock_hold (s);write_unlock_bh (&x25_list_lock);lock_sock (s);
net/x25/af_x25.c void x25_kill_by_neigh(struct x25_neigh *nb) · line 1786
Quoted 10 lines
net/x25/af_x25.c +4
-2-x25_disconnect (s,ENETUNREACH ,0 ,0 ); +if (x25_sk (s)->neighbour == nb) +x25_disconnect (s,ENETUNREACH ,0 ,0 );release_sock (s); -write_lock_bh (&x25_list_lock); +sock_put (s); + goto again; } }write_unlock_bh (&x25_list_lock);
Note that sk will stay on list (with NULL neigh) even after disconnect and the above introduces a quadratic behavior, but I can't find an easy way to avoid it.
/P
This patch was applied to netdev/net.git (main) by Paolo Abeni <[email protected]>:
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <[email protected]>:
Quoted 11 lines · On Mon, 13 Jul 2026 10:47:50 +0000 you wrote:
x25_kill_by_neigh()walks the global X.25 socket list looking for sockets attached to a terminating neighbour.x25_list_lockprotects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped.The function currently drops
x25_list_lockbefore callinglock_sock(s). A concurrent close can runx25_release(), remove the same socket fromx25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/structx25_sock.[...]
Here is the summary with links:
- [net] net/x25: fix use-after-free in x25_kill_by_neigh()
https://git.kernel.org/netdev/net/c/5499e0602d2f
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html