CVE-2026-68188: Bluetooth: RFCOMM: Fix session UAF in set_termios
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 2894bd8c68e97accd758ca6e5fc375d7e9e8882c, 4eac4576a072084b06459de6c054b4ebc764b4ea, 780b04d09c941262ee2a2b4a09906451b69df8a6; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2894bd8c68e97accd758ca6e5fc375d7e9e8882c, 4eac4576a072084b06459de6c054b4ebc764b4ea, 780b04d09c941262ee2a2b4a09906451b69df8a6; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.14affected
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before 4eac4576a072084b06459de6c054b4ebc764b4eaaffected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before 82c383f9031f1ce919ac6c3c06bc5bd492a6b078affected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before c5c060597247131f90f39ea7c8c978fa0c2e79d0affected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before 2894bd8c68e97accd758ca6e5fc375d7e9e8882caffected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before a82a9d3891f5607030b0672c255087a12bb9837baffected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before 780b04d09c941262ee2a2b4a09906451b69df8a6affected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607eaaffected · git
- 3a5e903c09aed19ca4a1bb26d87b8d6461a93818 and later · before c783399efc22d035443f1dfbf2a09bf9562aaa5eaffected · git
- before 2.6.14not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-extra | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-debug-uki-virt | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-devel | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-devel-matched | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-headers | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-modules | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-modules-core | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-modules-extra | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-modules-extra-matched | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-rt | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-rt-64k | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
| AlmaLinux:10 | kernel-rt-64k-core | before 6.12.0-211.58.1.el10_2 | 6.12.0-211.58.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68186Aug 10, 2026 · binfmt_misc: set have_execfd only once the interpreter is opened0Monitor
- ← EarlierCVE-2026-68187Aug 10, 2026 · exec: fix unsigned loop counter wrap in transfer_args_to_stack()0Monitor
- Later →CVE-2026-68189Aug 10, 2026 · Bluetooth: hci_sync: Protect UUID list traversal31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2894bd8c68e97accd758ca6e5fc375d7e9e8882c | Vendor (CNA) |
| Linux Linux | 4eac4576a072084b06459de6c054b4ebc764b4ea | Vendor (CNA) |
| Linux Linux | 780b04d09c941262ee2a2b4a09906451b69df8a6 | Vendor (CNA) |
| Linux Linux | 82c383f9031f1ce919ac6c3c06bc5bd492a6b078 | Vendor (CNA) |
| Linux Linux | 98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea | Vendor (CNA) |
| Linux Linux | a82a9d3891f5607030b0672c255087a12bb9837b | Vendor (CNA) |
| Linux Linux | c5c060597247131f90f39ea7c8c978fa0c2e79d0 | Vendor (CNA) |
| Linux Linux | c783399efc22d035443f1dfbf2a09bf9562aaa5e | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.166.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+7
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4eac4576a072084b06459de6c054b4ebc764b4ea
- git.kernel.org/stable/c/780b04d09c941262ee2a2b4a09906451b69df8a6
- git.kernel.org/stable/c/82c383f9031f1ce919ac6c3c06bc5bd492a6b078
- git.kernel.org/stable/c/98bc68194e37bfa5e8ddc80b5c1eb0be4dc607ea
- git.kernel.org/stable/c/a82a9d3891f5607030b0672c255087a12bb9837b
- git.kernel.org/stable/c/c5c060597247131f90f39ea7c8c978fa0c2e79d0
- git.kernel.org/stable/c/c783399efc22d035443f1dfbf2a09bf9562aaa5e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.