CVE-2024-23363
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 processing an improperly formatted Fine Time Measurement (FTM) management frame.
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 vulnerability exists in the processing of Fine Time Measurement (FTM) management frames as defined in the 802.11mc Wi-Fi standard. When the system processes an improperly formatted FTM frame, it triggers a transient denial of service condition, likely due to a parsing or validation error that causes a crash, hang, or resource exhaustion.
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 Qualcomm Wi-Fi chipset in useCheck system documentation, network adapter details, or run commands like 'lspci', 'iw list', or 'nmcli device show' to identify the wireless hardware model and firmware versionAffected if The system uses any of the following chips: Ar8035, Csr8811, Fastconnect 6900, Fastconnect 7800, Immersive Home 214, Immersive Home 216, Immersive Home 316, or Immersive Home 318
-
Verify if FTM (802.11mc) functionality is enabledCheck Wi-Fi configuration settings or use commands like 'iw list' to examine supported features, or check if FTM responder or FTM initiator is actively configuredAffected if FTM functionality is enabled or active on the wireless interface
-
Monitor for Wi-Fi daemon crashes or instabilityReview system logs (journalctl, dmesg, syslog) for entries related to Wi-Fi driver crashes, kernel panics, or unexpected wireless interface drops occurring after FTM frame exchangesAffected if Wi-Fi crashes, hangs, or resource exhaustion events correlate with FTM frame processing
-
Check for FTM-related error messages in kernel logsSearch logs for patterns such as 'FTM', '802.11mc', 'fine timing measurement', or parsing errors in wireless driver messagesAffected if Error logs indicate FTM frame parsing failures or validation errors
A system is affected if it uses any of the listed Qualcomm firmware chipsets AND has FTM (802.11mc) functionality enabled, with observed Wi-Fi instability or DoS conditions.
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 affected WiFi drivers or firmware that properly validate and handle FTM management frame parsing. If no patch is available, consider disabling FTM functionality if not required.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23363 — 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-23363 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