CVE-2026-68188
Vulnérabilité non évaluée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2026-68188 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.22 %, ce qui la place devant 11.4 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.12.101, <2.6.14, 0, <=7.1.*, <98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea, 5.15.216, <=5.10.*, <=6.6.*, 2.6.14, 6.18.42, <c5c060597247131f90f39ea7c8c978fa0c2e79d0, 7.1.6, 6.1.183, <=6.18.*, <780b04d09c941262ee2a2b4a09906451b69df8a6, <a82a9d3891f5607030b0672c255087a12bb9837b, 3a5e903c09aed19ca4a1bb26d87b8d6461a93818, <4eac4576a072084b06459de6c054b4ebc764b4ea, <=*, <=5.15.*, <c783399efc22d035443f1dfbf2a09bf9562aaa5e, 5.10.265, 6.6.148, 7.2, <2894bd8c68e97accd758ca6e5fc375d7e9e8882c, <82c383f9031f1ce919ac6c3c06bc5bd492a6b078) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- https://git.kernel.org/stable/c/4eac4576a072084b06459de6c054b4ebc764b4ea
- https://git.kernel.org/stable/c/82c383f9031f1ce919ac6c3c06bc5bd492a6b078
- https://git.kernel.org/stable/c/c5c060597247131f90f39ea7c8c978fa0c2e79d0
- https://git.kernel.org/stable/c/2894bd8c68e97accd758ca6e5fc375d7e9e8882c
- https://git.kernel.org/stable/c/a82a9d3891f5607030b0672c255087a12bb9837b
- https://git.kernel.org/stable/c/780b04d09c941262ee2a2b4a09906451b69df8a6
- https://git.kernel.org/stable/c/98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea
- https://git.kernel.org/stable/c/c783399efc22d035443f1dfbf2a09bf9562aaa5e
