{"id":"CVE-2026-98290","published":"2026-10-06T09:18:19.317","lastModified":"2026-10-07T07:17:08.210","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: avoid socket lock inversion in listener cleanup\n\nrfcomm_sock_cleanup_listen() closes unaccepted child sockets through\nrfcomm_sock_close(), which takes the child socket lock before\nrfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these\nlocks in reverse order while handling connections and DLC state changes,\nso lockdep reports a possible deadlock.\n\nClose dequeued children without taking their socket lock. The accept queue\nowns a reference to each child, and bt_accept_dequeue() locks the child\nwhile unlinking it and clearing its parent pointer.\n\nDropping the child lock makes it important to prevent a concurrent\nrfcomm_connect_ind() from enqueueing a new child after cleanup observes an\nempty queue. Set a listening socket to BT_CLOSED while its lock is still\nheld, before dropping the lock and draining the queue. The state check in\nrfcomm_connect_ind() then rejects new children once cleanup starts.","cvssScore":7.5,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def","tags":[]},{"url":"https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523","tags":[]},{"url":"https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4","tags":[]},{"url":"https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254","tags":[]},{"url":"https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a","tags":[]},{"url":"https://git.kernel.org/stable/c/c741977e413f5b49d306700820fb55ccb8269f5a","tags":[]},{"url":"https://git.kernel.org/stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":{"summary":"This vulnerability occurs when Bluetooth RFCOMM listener cleanup closes unaccepted child sockets in the wrong order, potentially causing a deadlock between socket locks and the RFCOMM mutex. This can lead to system instability or denial of service when handling Bluetooth connections.","exploitability":"Exploitation is moderately difficult as it requires precise timing and specific Bluetooth connection patterns to trigger the lock inversion scenario, but does not require user interaction or elevated privileges.","blast_radius":"The impact could affect any Linux system running Bluetooth services with active RFCOMM listeners, potentially causing denial of service for Bluetooth connectivity and related services until system restart.","remediation":"Upgrade to Linux kernel version 6.10 or later which contains the fix for this RFCOMM lock inversion issue.","detection":"No reliable host or network indicator is derivable from the published description.","tags":["bluetooth","kernel","denial-of-service","lock-inversion"],"model":"garnet-coder","analyzedAt":"2026-10-15T09:06:14.033Z"}}