Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_list under the list lock, but returns the selected listener after dropping that lock without taking a reference. rfcomm_connect_ind() then locks the listener, queues a child socket on it, and may notify it after unlocking it. The buggy scenario involves two paths, with each column showing the order within that path: rfcomm_connect_ind(): listener close: 1. Find parent in 1. close() enters rfcomm_get_sock_by_channel() rfcomm_sock_release(). 2. Drop rfcomm_sk_list.lock 2. rfcomm_sock_shutdown() without pinning parent. closes the listener. 3. Call lock_sock(parent) and 3. rfcomm_sock_kill() bt_accept_enqueue(parent, unlinks and puts parent. sk, true). 4. Read parent flags and may 4. parent can be freed. call sk_state_change(). If close wins the race, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup callback. Take a reference on the listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN before queueing a child, cache the deferred-setup bit while the parent is locked, and drop the reference after the last parent use. KASAN reported a slab-use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the freeing stack going through rfcomm_sock_kill() and rfcomm_sock_release().

Affected products

VendorProductVersions
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <f5ec76bdbeb80f75ad0be204371afffee0f8fac8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <a07d741c077d4e34b16458241a94d29039386553; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <1f73f92f66251065a5f39b09a47cf05ea14d3107; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <de31973ef00e5aa55496f84cf6a44bb157a34e02; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <b0e33e409715c617e2a20f46f99aa5403a14dfda; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <8802413ce63175fb522a2bd609fb043a3550c720; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <6f4462d12133106460d7c046b95aad2491e3fddf; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <43c441edacf953b39517a44f5e5e10a93618b226
LinuxLinux2.6.12; 0 to <2.6.12; 5.10.259 to <=5.10.*; 5.15.210 to <=5.15.*; 6.1.176 to <=6.1.*; 6.6.143 to <=6.6.*; 6.12.94 to <=6.12.*; 6.18.36 to <=6.18.*; 7.0.13 to <=7.0.*; 7.1 to <=*

References

Authoritative sources

This page is a snapshot. For the latest enrichment and updates, view the record on CVE.org or the NVD.

Generated from the official CVE List on 25 Jun 2026 10:14 UTC.