Answer in brief
CVE-2026-98739 records a Unknown severity vulnerability in Bluetooth: RFCOMM: Fix initial port reference race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=80ea73378af46b0023eb2f400d26c2a60248ffaa <a03ccf1ab77380d4c4a3c56552e12de4a83efa21 || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <0a554901bd227537f79220443b2b36d585d62893 || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <2d696c1ed3468dcb62578a3911e687110d463520 | a03ccf1ab77380d4c4a3c56552e12de4a83efa21, 0a554901bd227537f79220443b2b36d585d62893, e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b, 2d696c1ed3468dcb62578a3911e687110d463520 |
| Linux/Linuxgeneric | 3.15 | Not reported |
| Linux/Linuxgeneric | >=80ea73378af46b0023eb2f400d26c2a60248ffaa <55d162aa00d1ee33c3e6fa88b71f1e2d6e1441e9 || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <a03ccf1ab77380d4c4a3c56552e12de4a83efa21 || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <0a554901bd227537f79220443b2b36d585d62893 || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b || >=80ea73378af46b0023eb2f400d26c2a60248ffaa <2d696c1ed3468dcb62578a3911e687110d463520 | 55d162aa00d1ee33c3e6fa88b71f1e2d6e1441e9, a03ccf1ab77380d4c4a3c56552e12de4a83efa21, 0a554901bd227537f79220443b2b36d585d62893, e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b, 2d696c1ed3468dcb62578a3911e687110d463520 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.