CVE-2024-23364
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 when processing the non-transmitted BSSID profile sub-elements present within the MBSSID Information Element (IE) of a beacon frame that is received from over-the-air (OTA).
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 high-severity denial-of-service vulnerability exists in wireless device firmware where processing of malformed MBSSID (Multiple BSSID) Information Elements in OTA beacon frames causes a transient service disruption. Specifically, the parser for non-transmitted BSSID profile sub-elements within the MBSSID IE lacks proper bounds checking or validation, allowing a specially crafted beacon frame received over-the-air to trigger a crash or hang condition in the wireless stack.
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
- 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 wireless chipset modelAccess the device firmware UI, CLI, or kernel modules to determine the exact Qualcomm chipset in use (e.g., Ar8035, Fastconnect 6200/6700/6800/6900, Qca6777aq, Qca6787aq, Qca6797aq)Affected if The device uses any of the following chipsets: Ar8035, Fastconnect 6200, Fastconnect 6700, Fastconnect 6800, Fastconnect 6900, Qca6777aq, Qca6787aq, or Qca6797aq
-
Check MBSSID feature statusInspect the wireless interface configuration for MBSSID or EMA (Enhanced Multiband Operation) settings via CLI (e.g., iwconfig, iw dev), web UI, or vendor management interfaceAffected if MBSSID or EMA feature is enabled on the wireless interface
-
Verify beacon frame processingCapture and analyze beacon frames using a wireless sniffer (e.g., Wireshark, Kismet) to observe how the device handles MBSSID Information ElementsAffected if The device processes MBSSID IEs from beacon frames without apparent crashes or hangs (or conversely, if disconnections are occurring)
-
Monitor for crash indicatorsReview system logs, kernel messages (dmesg), or wireless subsystem logs for unexpected wireless stack crashes, hangs, or client disconnections coinciding with beacon frame receptionAffected if Wireless stack crashes, hangs, or repeated client disconnections occur after receiving beacon frames containing MBSSID IEs
A user is affected if their device contains any of the listed Qualcomm chipsets AND has MBSSID/EMA feature enabled, as this combination triggers the vulnerable parser code path for malformed MBSSID Information Elements in beacon frames.
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 dataOrganizations should apply vendor-supplied firmware updates for affected wireless access points and client devices. As an interim control, disable MBSSID/EMA (Enhanced Multiband Operation) features if not required, and monitor for unexpected wireless client disconnections that may indicate exploitation attempts.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23364 — 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-2024-23364 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