CVE-2026-98290Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
- 7.5HighCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup rfcomm_sock_cleanup_listen() closes unaccepted child sockets through rfcomm_sock_close(), which takes the child socket lock before rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these locks in reverse order while handling connections and DLC state changes, so lockdep reports a possible deadlock. Close dequeued children without taking their socket lock. The accept queue owns a reference to each child, and bt_accept_dequeue() locks the child while unlinking it and clearing its parent pointer. Dropping the child lock makes it important to prevent a concurrent rfcomm_connect_ind() from enqueueing a new child after cleanup observes an empty queue. Set a listening socket to BT_CLOSED while its lock is still held, before dropping the lock and draining the queue. The state check in rfcomm_connect_ind() then rejects new children once cleanup starts.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.5 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < 4aafb47301a799d3e01230d6568c4e93524e1523
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < c741977e413f5b49d306700820fb55ccb8269f5a
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < c6792c441767256030606eb82dca5d5fc360dd9a
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < bfce253f039eb5f58b810af267942a9f59207254
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < 18174b166547ef41973cc19feb5ef9cab39a8def
- affected b7ce436a5d798bc59e71797952566608a4b4626b – < 801fb950cae7048eb7d83b18857d1ca37b8cd5a4
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c (opens in a new tab)
- https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523 (opens in a new tab)
- https://git.kernel.org/stable/c/c741977e413f5b49d306700820fb55ccb8269f5a (opens in a new tab)
- https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a (opens in a new tab)
- https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254 (opens in a new tab)
- https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def (opens in a new tab)
- https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93218 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98290)Record last updated .