Kernel fault via stale deferred-setup session
Published Oct 18, 2026 · Updated Oct 18, 2026
NULL dereference in Linux Bluetooth RFCOMM allows attackers to trigger a kernel fault via deferred-setup connection teardown. The RFCOMM_CONNINFO handler follows dlc->session after a peer disconnect clears it, because the deferred-setup flag still bypasses the connected-state check. A Bluetooth peer must reach an accepted BT_DEFER_SETUP socket, and a local application must subsequently request connection information; the demonstrated consequence is a kernel oops, not code execution.
Summary
What happened
NULL dereference in Linux Bluetooth RFCOMM allows attackers to trigger a kernel fault via deferred-setup connection teardown. The RFCOMM_CONNINFO handler follows dlc->session after a peer disconnect clears it, because the deferred-setup flag still bypasses the connected-state check. A Bluetooth peer must reach an accepted BT_DEFER_SETUP socket, and a local application must subsequently request connection information; the demonstrated consequence is a kernel oops, not code execution.
The record
- CVE
- CVE-2026-98455
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.30
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <005b23d9e324fe5d0acbcfa70c625f2e81189046
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <1c4f7e1177da2f229be04139c27e5370a1cfba52
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <46f8ffd0a1f1eb6cbc94946a92c11ef601e228a1
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <4bf5ca47203049ce3648f750a53dcdc98bcc9e3e
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <84ae3cfd7d3a63591a2eb4faa24faf678c6708aa
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <8f5b30cc12c409ff62891e47ed51e6bf0945a3ea
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <c3aee3fc1287c8a555baf3895959087cb0c33fe8
- Affected versionversion=bb23c0ab824653be4aa7dfca15b07b3059717004 <c7362f6a18ed167f52f08ce25eeec8a7818c5004
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started