Memory corruption via uncleared pending GATT operation
Published Nov 4, 2021 · Updated Nov 4, 2025
Use-after-free in BlueZ 5.40 through 5.61 allows remote attackers to corrupt memory by disconnecting during a GATT WriteValue call. The GATT database leaves an asynchronous D-Bus operation pending without disconnect cleanup, allowing its reply path to use device state released with the client connection. Reachability requires a Bluetooth client connection to the GATT server and precise disconnection during processing; published sources do not establish whether the corruption produces a crash, data access, or code execution.
Summary
What happened
Use-after-free in BlueZ 5.40 through 5.61 allows remote attackers to corrupt memory by disconnecting during a GATT WriteValue call. The GATT database leaves an asynchronous D-Bus operation pending without disconnect cleanup, allowing its reply path to use device state released with the client connection. Reachability requires a Bluetooth client connection to the GATT server and precise disconnection during processing; published sources do not establish whether the corruption produces a crash, data access, or code execution.
The record
- CVE
- CVE-2021-43400
- Published
- Nov 4, 2021
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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