Local service interruption via recursive RFCOMM locking
Published Oct 21, 2024 · Updated May 12, 2026
Improper locking in Linux Bluetooth RFCOMM allows local users to interrupt service by triggering a socket-state deadlock. rfcomm_sock_ioctl calls rfcomm_sk_state_change while holding the socket lock, and that callback tries to acquire the same lock again during RFCOMM closure. Triggering the condition requires local low-privileged access to the RFCOMM socket path; the consequence is bounded to availability, including the Siemens embedded GNU/Linux subsystem.
Summary
What happened
Improper locking in Linux Bluetooth RFCOMM allows local users to interrupt service by triggering a socket-state deadlock. rfcomm_sock_ioctl calls rfcomm_sk_state_change while holding the socket lock, and that callback tries to acquire the same lock again during RFCOMM closure. Triggering the condition requires local low-privileged access to the RFCOMM socket path; the consequence is bounded to availability, including the Siemens embedded GNU/Linux subsystem.
The record
- CVE
- CVE-2024-50044
- Published
- Oct 21, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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.
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