CVE-2026-68188

Bluetooth: RFCOMM: Fix session UAF in set_termios

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix session UAF in set_termios rfcomm_tty_set_termios() tests dlc->session without rfcomm_mutex and later passes the pointer to rfcomm_send_rpn(). The latter dereferences both session->initiator and session->sock. Meanwhile, krfcommd can unlink the DLC and free the session while holding rfcomm_mutex. The race can proceed as follows: TTY ioctl task krfcommd -------------- -------- load dlc->session enter rfcomm_send_rpn() lock rfcomm_mutex clear dlc->session free session unlock rfcomm_mutex read session->initiator KASAN reported: BUG: KASAN: slab-use-after-free in rfcomm_send_rpn+0x297/0x2a0 Read of size 4 at addr ffff88810012a850 by task poc/92 Call Trace: rfcomm_send_rpn+0x297/0x2a0 rfcomm_tty_set_termios+0x50d/0x850 tty_set_termios+0x596/0x950 set_termios+0x46a/0x6e0 tty_mode_ioctl+0x152/0xbd0 tty_ioctl+0x915/0x1240 __x64_sys_ioctl+0x134/0x1c0 Allocated by task 92: rfcomm_session_add+0x9e/0x2e0 rfcomm_dlc_open+0x8b1/0xe00 rfcomm_dev_activate+0x85/0x1a0 rfcomm_tty_open+0x90/0x280 Freed by task 68: kfree+0x131/0x3c0 rfcomm_session_del+0x119/0x180 rfcomm_run+0x737/0x4710 Add rfcomm_dlc_send_rpn(), which holds rfcomm_mutex while it verifies that the DLC is still attached and sends the RPN frame. Have the TTY path use the helper and drop its unlocked session check. This keeps the session valid through both the frame construction and socket send.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.14 ≤ v < 5.10.2652.6.14 ≤ v < 5.15.2162.6.14 ≤ v < 6.1.1832.6.14 ≤ v < 6.12.1012.6.14 ≤ v < 6.18.422.6.14 ≤ v < 6.6.1482.6.14 ≤ v < 7.1.62.6.14 ≤ v < 7.22.6.143a5e903c09aed19ca4a1bb26d87b8d6461a93818
Vendor states this is fixed in 2894bd8c68e97accd758ca6e5fc375d7e9e8882c (fixed)
Vendor states this is fixed in 4eac4576a072084b06459de6c054b4ebc764b4ea (fixed)
Vendor states this is fixed in 780b04d09c941262ee2a2b4a09906451b69df8a6 (fixed)
Vendor states this is fixed in 82c383f9031f1ce919ac6c3c06bc5bd492a6b078 (fixed)
Vendor states this is fixed in 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea (fixed)
Vendor states this is fixed in a82a9d3891f5607030b0672c255087a12bb9837b (fixed)
Vendor states this is fixed in c5c060597247131f90f39ea7c8c978fa0c2e79d0 (fixed)
Vendor states this is fixed in c783399efc22d035443f1dfbf2a09bf9562aaa5e (fixed)
Vendor states this is fixed in 2.6.14 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card