Adjacent service crash via unreleased SDP buffers
Published Nov 12, 2021 · Updated Nov 4, 2025
Resource exhaustion in BlueZ 5.58 allows physically proximate attackers to crash the Bluetooth service by flooding it with SDP packets. sdp_cstate_alloc_buf allocates data buffers for continuation states, links them into the cstates list, and fails to release them after their effective lifetime. The attack requires Bluetooth proximity and repeated SDP traffic; memory consumption grows over time until the service crashes, without reported data exposure or modification.
Summary
What happened
Resource exhaustion in BlueZ 5.58 allows physically proximate attackers to crash the Bluetooth service by flooding it with SDP packets. sdp_cstate_alloc_buf allocates data buffers for continuation states, links them into the cstates list, and fails to release them after their effective lifetime. The attack requires Bluetooth proximity and repeated SDP traffic; memory consumption grows over time until the service crashes, without reported data exposure or modification.
The record
- CVE
- CVE-2021-41229
- Published
- Nov 12, 2021
- Updated
- Nov 4, 2025
- Vendor
- BlueZ
- Product
- BlueZ
- Classifications
- CWE-400, CWE-401, T1499.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2021CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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== 5.58
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