Availability loss via unchecked Bluetooth GPIO error pointer
Published Mar 1, 2023 · Updated Mar 20, 2025
NULL pointer dereference in Linux kernel before 5.16.3 allows local users to interrupt service during QCA Bluetooth device probing. The qca_serdev_probe function checks optional GPIO descriptors only for NULL, allowing error pointers to pass as usable handles. Reachability requires a QCA Bluetooth device and a GPIO acquisition error during driver probing; the documented consequence is availability loss only.
Summary
What happened
NULL pointer dereference in Linux kernel before 5.16.3 allows local users to interrupt service during QCA Bluetooth device probing. The qca_serdev_probe function checks optional GPIO descriptors only for NULL, allowing error pointers to pass as usable handles. Reachability requires a QCA Bluetooth device and a GPIO acquisition error during driver probing; the documented consequence is availability loss only.
The record
- CVE
- CVE-2023-23002
- Published
- Mar 1, 2023
- Updated
- Mar 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 20, 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