KernelScan.io

HIGH Introduced in 3.10

rfcomm SecurityCfm UAF

CVE-2026-89569

CVSS 8.8 / 10.0 NVD

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.5HIGH

01

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: serialize security confirmation handling rfcomm_security_cfm() looks up a session on session_list and then walks its DLC list without holding rfcomm_mutex. Since RFCOMM session teardown uses rfcomm_mutex, krfcommd can close and free the same session and DLCs concurrently: hci_rx_work krfcommd ----------- --------- rfcomm_session_get() rfcomm_lock() rfcomm_session_close() rfcomm_dlc_unlink() rfcomm_session_del() kfree(s) rfcomm_unlock() walk s->dlcs The callback can then read a freed session list head and touch freed DLCs while updating their flags or timers. Serialize the session lookup and DLC traversal in rfcomm_security_cfm() with rfcomm_mutex. This matches the existing RFCOMM session lifetime rules and prevents concurrent rfcomm_session_del() / rfcomm_dlc_unlink() from tearing the objects down while the callback is using them. KASAN reported: BUG: KASAN: slab-use-after-free in rfcomm_security_cfm+0x41c/0x440 Read of size 8 at addr ffff888111fb3960 by task kworker/u17:1/89 Workqueue: hci0 hci_rx_work Call Trace: rfcomm_security_cfm+0x41c/0x440 hci_encrypt_cfm+0x139/0x590 hci_encrypt_change_evt+0x37b/0xc40 hci_event_packet+0x71b/0xb20 hci_rx_work+0x293/0x730 Allocated by task 69: rfcomm_session_add+0x9e/0x2f0 rfcomm_run+0x44b/0x41e0 Freed by task 69: kfree+0x131/0x3c0 rfcomm_session_del+0x188/0x220 rfcomm_run+0x1985/0x41e0

02

Engine v0.6.0

Risk summary

Any device with an active Bluetooth stack is at risk from a nearby attacker who can trigger a Bluetooth connection. The race condition between security confirmation handling and session teardown leads to use-after-free of kernel heap objects, potentially causing memory corruption or a kernel crash. Exploitation requires proximity and winning a narrow race window.

Affectednet/bluetooth/rfcomm/core.c (Bluetooth RFCOMM)

Vulnerability analysis

The Bluetooth RFCOMM subsystem handles security confirmations from the controller without protecting the list of active sessions and their connections. While one kernel thread is walking those lists, another thread can finish tearing down and freeing the same memory, causing a use-after-free. The fix adds locking around the confirmation handling to match the teardown path, preventing the session from being freed while the callback is still using it. The bug is triggered when the kernel processes a Bluetooth encryption event during connection setup, so any nearby Bluetooth peer can reach it, and a local process initiating Bluetooth connections can as well.

03

BranchIntroducedFixed inPatch commit
5.103.105.10.27062ce8b33eb23
5.153.105.15.2213873f3449701
6.13.106.1.1887ded32641064
6.123.106.12.1091b7841ffad08
6.183.106.18.50946d76db77ee
6.63.106.6.15782425b14f0fb
7.23.107.2.4fbf7961964a6
mainline3.107.3759c185d0bbd
cip/5.103.105.10.271-cip7862ce8b33eb23
cip/6.13.106.1.189-cip617ded32641064
cip/6.1-rt3.106.1.189-cip61-rt327ded32641064
cip/6.123.106.12.111-cip321b7841ffad08

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip136)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip136-rt50)
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip115)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)