CVE-2026-98739

Bluetooth: RFCOMM: Fix initial port reference race

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix initial port reference race For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference. The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible: 1. Install and release each obtain a reference with rfcomm_dev_get(). 2. Release observes RFCOMM_TTY_OWNED clear. 3. Install sets RFCOMM_TTY_OWNED and drops the initial reference. 4. Release drops the same initial reference again. 5. TTY cleanup drops its reference and frees the device. 6. Release performs its final tty_port_put() on the freed port. KASAN reported: BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190 Write of size 4 at addr ffff8881001d3d5c by task poc/92 Call Trace: tty_port_put+0x22/0x190 rfcomm_dev_ioctl+0x1d4/0x1930 sock_do_ioctl+0x110/0x260 sock_ioctl+0x380/0x590 __x64_sys_ioctl+0x134/0x1c0 Allocated by task 88: rfcomm_dev_ioctl+0x8f6/0x1930 sock_do_ioctl+0x110/0x260 sock_ioctl+0x380/0x590 __x64_sys_ioctl+0x134/0x1c0 Freed by task 65: kfree+0x131/0x3c0 rfcomm_dev_destruct+0x23b/0x2f0 release_one_tty+0xc1/0x370 process_one_work+0x661/0x1090 Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.

Key facts

Published
18 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.176% likely to be exploited in the next 30 days, higher than 7.248% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding cd247e38b14df48d6b3940c4573a9f7acb10c363 (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding d3dd18e85c140df72e0f2b5ee156ebfba04c06cb (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding c50360a019766fafa27318928bfea96dcce8a37d (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding 55d162aa00d1ee33c3e6fa88b71f1e2d6e1441e9 (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding a03ccf1ab77380d4c4a3c56552e12de4a83efa21 (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding 0a554901bd227537f79220443b2b36d585d62893 (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b (affected)
  • 80ea73378af46b0023eb2f400d26c2a60248ffaa up to but excluding 2d696c1ed3468dcb62578a3911e687110d463520 (affected)
LinuxLinux
  • Default status: affected
  • 3.15 (affected)
  • 0 up to but excluding 3.15 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References