CVE-2023-43532
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 · uneditedMemory corruption while reading ACPI config through the user mode app.
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 confidenceMemory corruption vulnerability in the ACPI (Advanced Configuration and Power Interface) configuration reading path, triggered through a user-mode application. The vulnerability allows local attackers to corrupt memory via the ACPI config parsing, likely due to improper bounds checking or validation during the read operation.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Qualcomm Fastconnect wireless hardware presenceCheck system information or device manager for Qualcomm Fastconnect 6700, 6900, or 7800 network adapters. On Linux, run 'lspci' or 'lsusb' and look for Qualcomm wireless devices.Affected if Any Fastconnect 6700, 6900, or 7800 wireless hardware is present in the system
-
Identify Qualcomm Snapdragon compute platform presenceCheck system BIOS/UEFI information or run 'dmidecode' to look for Snapdragon 7c+ Gen 3 or 8cx Gen 3 platform components.Affected if Any Snapdragon 7c+ Gen 3 or 8cx Gen 3 compute platform is present
-
Identify Qualcomm Wcd audio codec presenceCheck system audio device information for Wcd9380 or Wcd9385 audio codec components.Affected if Wcd9380 or Wcd9385 audio codec is present in the system
-
Check firmware version of Qualcomm componentsUse vendor-specific tools (such as Qualcomm firmware update utilities, UEFI firmware tools, or system information utilities) to retrieve the current firmware version of the identified Qualcomm components.Affected if The firmware version matches any of the affected products (Fastconnect 6700/6900/7800, Sc8380xp, Snapdragon 7c+ Gen 3, Snapdragon 8cx Gen 3, Wcd9380, Wcd9385)
-
Verify ACPI configuration access is available to user-mode applicationsCheck if ACPI device nodes or configuration interfaces are exposed and accessible to non-privileged user applications. Review ACPI table access permissions and any exposed ACPI configuration reading interfaces.Affected if User-mode applications can trigger ACPI configuration reading operations
A system is affected if it contains any of the listed Qualcomm firmware components (Fastconnect, Snapdragon, Sc8380xp, or Wcd audio codecs) and allows user-mode access to ACPI configuration reading functionality.
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 dataApply vendor-provided patches for firmware, UEFI, or associated system software that addresses the ACPI config parsing vulnerability. Since this is memory corruption with CVSS 7.8, prioritize patching systems with local untrusted code execution risk.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43532 — 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-43532 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