CVE-2026-68188

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

References (8)

Vendor Advisories for CVE-2026-68188(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:6.12.0-211.58.1.el10_22026-09-23redhat
redhatkernel-0:5.14.0-687.50.1.el9_82026-09-23redhat
redhatkernel-rt-0:4.18.0-553.166.1.rt7.507.el8_102026-09-22redhat
redhatkernel-0:4.18.0-553.166.1.el8_102026-09-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 05:25 UTCVendor advisory
  3. 2026-10-04 05:25 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 22:41 UTCEG score recompute
  8. 2026-09-30 22:41 UTCVendor advisory
  9. 2026-09-30 22:41 UTCGHSA enrichment
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 16:57 UTCVendor advisory
  13. 2026-09-27 16:57 UTCGHSA enrichment
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-23 21:13 UTCVendor advisory
  17. 2026-09-23 21:13 UTCGHSA enrichment
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-20 21:24 UTCVendor advisory
  20. 2026-09-20 21:24 UTCGHSA enrichment
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-18 00:50 UTCVendor advisory
  24. 2026-09-18 00:50 UTCGHSA enrichment
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 58 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 00:42 UTCVendor advisory
  3. 2026-09-15 00:42 UTCGHSA enrichment
  4. 2026-09-12 02:26 UTCVendor advisory
  5. 2026-09-12 02:26 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-09 05:54 UTCVendor advisory
  9. 2026-09-09 05:54 UTCGHSA enrichment
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 03:08 UTCVendor advisory
  14. 2026-09-06 03:08 UTCGHSA enrichment
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-03 06:34 UTCVendor advisory
  18. 2026-09-03 06:34 UTCGHSA enrichment
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-31 09:58 UTCVendor advisory
  22. 2026-08-31 09:57 UTCGHSA enrichment
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:42 UTCEPSS rescore
  26. 2026-08-28 11:43 UTCVendor advisory
  27. 2026-08-28 11:43 UTCGHSA enrichment
  28. 2026-08-26 14:47 UTCEPSS rescore
  29. 2026-08-25 13:49 UTCEPSS rescore
  30. 2026-08-25 10:31 UTCVendor advisory
  31. 2026-08-25 10:30 UTCGHSA enrichment
  32. 2026-08-23 00:19 UTCEPSS rescore
  33. 2026-08-22 13:58 UTCVendor advisory
  34. 2026-08-22 13:58 UTCGHSA enrichment
  35. 2026-08-21 23:49 UTCEPSS rescore
  36. 2026-08-20 22:56 UTCEPSS rescore
  37. 2026-08-19 17:25 UTCGHSA enrichment
  38. 2026-08-19 17:21 UTCNVD update
  39. 2026-08-19 17:04 UTCEPSS rescore
  40. 2026-08-19 16:55 UTCGHSA enrichment
  41. 2026-08-19 16:43 UTCMITRE cvelistV5
  42. 2026-08-18 13:49 UTCEPSS rescore
  43. 2026-08-18 13:49 UTCEPSS rescore
  44. 2026-08-17 13:47 UTCEPSS rescore
  45. 2026-08-17 05:38 UTCGHSA enrichment
  46. 2026-08-17 05:26 UTCNVD update
  47. 2026-08-17 05:10 UTCGHSA enrichment
  48. 2026-08-17 05:05 UTCMITRE cvelistV5
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 06:31 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 09:59 UTCEG score recompute
  54. 2026-08-13 09:59 UTCGHSA enrichment
  55. 2026-08-12 13:51 UTCEPSS rescore
  56. 2026-08-10 13:24 UTCNVD update
  57. 2026-08-10 12:20 UTCEG score recompute
  58. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-68188?
CVE-2026-68188 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix session UAF in set_termios rfcommttysettermios() tests dlc->session without rfcommmutex and later passes the pointer to rfcommsendrpn(). The latter dereferences both session->initiator and session->sock.…
When was CVE-2026-68188 disclosed?
CVE-2026-68188 was first published on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68188 actively exploited?
CVE-2026-68188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-68188?
A fix for CVE-2026-68188 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68188 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68188

Explore →

Is Your Infrastructure Affected by CVE-2026-68188?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs