Kernel crash via late HCI response
Published Apr 17, 2024 · Updated May 12, 2026
Null pointer dereference in Linux kernel RFCOMM before 6.8 allows local users to crash the system through a delayed HCI response. The RFCOMM receive path calls rfcomm_check_security after RFCOMM and L2CAP teardown, then dereferences conn->hcon after the L2CAP connection pointer has been released. Reachability requires low-privileged local access and a late Encryption Key Size response while HCI remains connected; the documented consequence is a kernel crash.
Summary
What happened
Null pointer dereference in Linux kernel RFCOMM before 6.8 allows local users to crash the system through a delayed HCI response. The RFCOMM receive path calls rfcomm_check_security after RFCOMM and L2CAP teardown, then dereferences conn->hcon after the L2CAP connection pointer has been released. Reachability requires low-privileged local access and a late Encryption Key Size response while HCI remains connected; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2024-26903
- Published
- Apr 17, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo