Test-process crash via unchecked failed response
Published Oct 17, 2022 · Updated Apr 15, 2025
Null pointer dereference in BlueZ 5.56 through 5.64 allows attackers to crash mgmt-tester via a failed controller-capability reply. The read_50_controller_cap_complete callback continues after a failed status, then accesses cap_len through a null response pointer. Reachability requires low-privileged adjacent access to the Bluetooth management path; the demonstrated consequence is termination of the test process.
Summary
What happened
Null pointer dereference in BlueZ 5.56 through 5.64 allows attackers to crash mgmt-tester via a failed controller-capability reply. The read_50_controller_cap_complete callback continues after a failed status, then accesses cap_len through a null response pointer. Reachability requires low-privileged adjacent access to the Bluetooth management path; the demonstrated consequence is termination of the test process.
The record
- CVE
- CVE-2022-3563
- Published
- Oct 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-404
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=n/a
What conditions does exploitation require?
What is affected?
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