CVE-2026-68188 — Bluetooth: RFCOMM: Fix session UAF in set_termios
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < 4eac4576a072084b06459de6c054b4ebc764b4ea≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < 82c383f9031f1ce919ac6c3c06bc5bd492a6b078≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < c5c060597247131f90f39ea7c8c978fa0c2e79d0≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < 2894bd8c68e97accd758ca6e5fc375d7e9e8882c≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < a82a9d3891f5607030b0672c255087a12bb9837b≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < 780b04d09c941262ee2a2b4a09906451b69df8a6≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea≥ 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and < c783399efc22d035443f1dfbf2a09bf9562aaa5e and 1 moreversion 2.6.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/c783399efc22d035443f1dfbf2a09bf9562aaa5e
- git.kernel.org/stable/c/a82a9d3891f5607030b0672c255087a12bb9837b
- git.kernel.org/stable/c/780b04d09c941262ee2a2b4a09906451b69df8a6
- git.kernel.org/stable/c/4eac4576a072084b06459de6c054b4ebc764b4ea
- git.kernel.org/stable/c/98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea
- git.kernel.org/stable/c/82c383f9031f1ce919ac6c3c06bc5bd492a6b078
- git.kernel.org/stable/c/2894bd8c68e97accd758ca6e5fc375d7e9e8882c
- git.kernel.org/stable/c/c5c060597247131f90f39ea7c8c978fa0c2e79d0
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68188 is "Bluetooth: RFCOMM: Fix session UAF in set_termios", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.