The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does     sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the     chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs     l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on     SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would     invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-     disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report,     over 1600+ raced iterations after it on bluetooth/master. (CVE-2026-53357)

Note that Nessus relies on the presence of the package as reported by the vendor.

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-53357

high Nessus Plugin ID 324896

Version 1.11

Version 1.10

Version 1.9

Version 1.8

Version 1.7

Version 1.5

Version 1.4

Version 1.3

Version 1.11 Aug 3, 2026, 1:05 PM CVSSv3 score source (changed from "CVE-2026-53357" to none) Plugin Feed: 202608031305
Version 1.10 Jul 29, 2026, 6:41 AM Detection (updated detection logic) Plugin Feed: 202607290641
Version 1.9 Jul 25, 2026, 1:06 PM CVSSv3 score source (set to "CVE-2026-53357") Detection (updated detection logic) Plugin metadata Plugin Feed: 202607251306
Version 1.8 Jul 21, 2026, 8:31 PM CVSSv3 score source (changed from "CVE-2026-53357" to none) Plugin Feed: 202607212031
Version 1.7 Jul 21, 2026, 12:41 AM CVSSv3 score source (set to "CVE-2026-53357") Detection (updated detection logic) Plugin Feed: 202607210041
Version 1.5 Jul 7, 2026, 11:10 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607071110
Version 1.4 Jul 6, 2026, 4:58 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607060458
Version 1.3 Jul 4, 2026, 4:43 PM CVSS metrics ("CVSSv2 score" set to none. "CVSSv2 vector" set to none. "CVSSv3 score" set to none. "CVSSv3 vector" set to none) CVSS temporal metrics ("CVSSv2 temporal vector" set to none. "CVSSv3 temporal vector" set to none) Detection (updated detection logic) New Plugin metadata Plugin Feed: 202607041643