CVE-2026-53357

Zwakheid

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces o

Getroffen producten

• linux linux_kernel

Bronnen

• https://git.kernel.org/stable/c/407217734835d21d4e0105ebf347860dc1806f88
• https://git.kernel.org/stable/c/5d86d2f1b4d9a508c441d3e45277ae1a73cfed57
• https://git.kernel.org/stable/c/751de6ec671fe75ad9cf65a0638d2a06b6a5984d
• https://git.kernel.org/stable/c/7eebd4c2c86f573af87ff165d08a83432eb0b919
• https://git.kernel.org/stable/c/87c543e2f78d0871f271df92dab98901bbd5b6f5
• https://git.kernel.org/stable/c/a5ca86a6097a8b030ca3226cd300b17ed330f966