CVE-2023-43512
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTransient DOS while parsing GATT service data when the total amount of memory that is required by the multiple services is greater than the actual size of the services buffer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA memory validation flaw in Bluetooth GATT service parsing causes a transient denial of service when the calculated memory requirements for multiple services exceed the allocated buffer size, leading to potential buffer overflow or service crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the hardware platformCheck if the system uses Qualcomm QCN7606 chipset. This may be visible in system information, hardware specs, or boot logs (dmesg, /proc/cpuinfo, or manufacturer documentation).Affected if The device is running on Qualcomm QCN7606 firmware and uses Bluetooth functionality.
-
Verify Bluetooth GATT service is activeCheck if Bluetooth is enabled and GATT services are running. On Linux: 'hciconfig -a' to list Bluetooth adapters, 'bluetoothctl list' to check adapter state, and check for GATT server processes or configurations.Affected if Bluetooth is enabled and a GATT server or profile is active, as the vulnerability is in GATT service parsing.
-
Inspect the number of GATT services configuredList active GATT services using 'btmon' or Bluetooth debugging tools. Count the number of services, characteristics, and descriptors being advertised or stored in memory.Affected if Multiple GATT services (more than a few) are configured, as the flaw triggers when memory calculations for multiple services exceed allocated buffer.
-
Check for Bluetooth-related crash or buffer error logsReview system logs (journalctl, dmesg, /var/log/syslog) for entries containing 'Bluetooth', 'GATT', 'buffer overflow', 'memory allocation failed', or crash indicators related to Bluetooth.Affected if Recent logs show Bluetooth crashes, GATT parsing errors, or memory allocation failures in Bluetooth stack.
-
Determine firmware versionQuery the Bluetooth firmware or baseband version via 'hciconfig -v', 'rfkill list', or vendor-specific tools. Compare against any available version information for the QCN7606.Affected if Running any version of Qualcomm QCN7606 firmware (all versions are affected per the advisory).
You are affected if you are running Qualcomm QCN7606 firmware with Bluetooth GATT services enabled, especially with multiple GATT services configured, as all firmware versions contain the memory validation flaw in GATT service parsing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper bounds checking and memory allocation validation before parsing GATT service data to ensure the buffer can accommodate all service descriptors.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-43512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data