In the Linux kernel, the following vulnerability has been resolved:
net/x25: fix use-after-free in x25killby_neigh()
x25killbyneigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25list_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 x25listlock before calling locksock(s). A concurrent close can run x25release(), remove the same socket from x25list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25sock.
Take sockhold(s) while x25listlock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25sk(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 x25killby_neigh().
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68137.json",
"cna_assigner": "Linux"
}