CVE-2023-43534
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 validating the TID to Link Mapping action request frame, when a station connects to an access point.
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 · high confidenceMemory corruption vulnerability in Wi-Fi access point firmware during validation of TID to Link Mapping action request frames used in Multi-Link Operation (802.11be/ax). The flaw occurs when a station connects to the AP, allowing potential remote code execution via malformed frames without authentication.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Wi-Fi firmware versionAccess the AP management interface or CLI and retrieve the Wi-Fi firmware/driver version information. For Qualcomm-based APs, this is often shown under Wireless > Firmware, System Information, or via 'wl -i iface ver' command.Affected if The version corresponds to any of these affected components: Ar8035, Fastconnect 6900, Fastconnect 7800, Flight Rb5 5g, Qam8255p, Qam8650p, Qam8775p, or Qamsrv1h firmware.
-
Verify AP mode is enabledCheck the device configuration to confirm it is operating as a Wi-Fi Access Point (not in client or station mode). This is typically found in Wireless Settings, Network Mode, or Interface Configuration.Affected if The device is configured and operating as a Wi-Fi Access Point (AP).
-
Confirm Multi-Link Operation feature statusCheck if Multi-Link Operation (802.11be/MLO) or 802.11ax Multi-Link support is enabled in the Wi-Fi configuration. This may appear as 'MLO', 'Multi-Link', '802.11be', or 'Multi-AP' settings.Affected if Multi-Link Operation (802.11be or 802.11ax MLO) is enabled on the AP.
-
Check for TID to Link Mapping configurationInspect the Wi-Fi advanced settings or action frame configuration for TID to Link Mapping parameters. This may be visible in debug logs, wireless diagnostics, or MLO-specific configuration panels.Affected if TID to Link Mapping or related Multi-Link action frame handling is active on the AP.
If the device uses any of the listed Qualcomm firmware components, operates as an Access Point, and has Multi-Link Operation (802.11be/ax MLO) enabled, the environment is affected by this vulnerability.
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-released firmware patches to affected access points; until patched, minimize exposure by restricting AP accessibility.
- Consultation4.0 h
- Implementation2.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43534 — 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-43534 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