CVE-2026-89569

CVE CVE-2026-89569EUVD EUVD-2026-76480Published 2026-09-11T19:44:38.000ZLast changed 2026-09-14T12:01:05.000ZCVSS 8.8

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 08c30aca9e698faddebd34f81e1196295f9dc063 <759c185d0bbdb131357408f50b8735e04ed3caff; 08c30aca9e698faddebd34f81e1196295f9dc063 <7ded3264106418c6456ccceaafd9fda596ce12c3; patch: 7.3-rc1; patch: 5.10.270; patch: 6.18.50; 08c30aca9e698faddebd34f81e1196295f9dc063 <946d76db77ee5f922968ce558629ae47b381e3fc; patch: 7.2.4; patch: 6.12.109; 08c30aca9e698faddebd34f81e1196295f9dc063 <82425b14f0fb22e46cfddc56d6465570f5ed0ce6; patch: 6.1.188; 08c30aca9e698faddebd34f81e1196295f9dc063 <fbf7961964a6e93360179f64712320ae9a1e9577; 3.10; patch: 6.6.157; patch: 0; 08c30aca9e698faddebd34f81e1196295f9dc063 <62ce8b33eb238cf18c15207332fbdc26d858f592; patch: 5.15.221; 08c30aca9e698faddebd34f81e1196295f9dc063 <3873f3449701b3dc98cba577923be6493598e7a1; 08c30aca9e698faddebd34f81e1196295f9dc063 <1b7841ffad08e911e8c4b9470f3fa08423568940

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.