Answer in brief
CVE-2026-68188 records a Unknown severity vulnerability in Bluetooth: RFCOMM: Fix session UAF in set_termios. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <2894bd8c68e97accd758ca6e5fc375d7e9e8882c || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <a82a9d3891f5607030b0672c255087a12bb9837b || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <780b04d09c941262ee2a2b4a09906451b69df8a6 || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <c783399efc22d035443f1dfbf2a09bf9562aaa5e | 2894bd8c68e97accd758ca6e5fc375d7e9e8882c, a82a9d3891f5607030b0672c255087a12bb9837b, 780b04d09c941262ee2a2b4a09906451b69df8a6, 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea, c783399efc22d035443f1dfbf2a09bf9562aaa5e |
| Linux/Linuxgeneric | 2.6.14 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68188 records a Unknown severity vulnerability in Bluetooth: RFCOMM: Fix session UAF in set_termios. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <2894bd8c68e97accd758ca6e5fc375d7e9e8882c || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <a82a9d3891f5607030b0672c255087a12bb9837b || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <780b04d09c941262ee2a2b4a09906451b69df8a6 || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea || >=3a5e903c09aed19ca4a1bb26d87b8d6461a93818 <c783399efc22d035443f1dfbf2a09bf9562aaa5e | 2894bd8c68e97accd758ca6e5fc375d7e9e8882c, a82a9d3891f5607030b0672c255087a12bb9837b, 780b04d09c941262ee2a2b4a09906451b69df8a6, 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea, c783399efc22d035443f1dfbf2a09bf9562aaa5e |
| Linux/Linuxgeneric | 2.6.14 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.