CVE-2023-28549
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 in WLAN HAL while parsing Rx buffer in processing TLV payload.
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 WLAN Hardware Abstraction Layer (HAL) that occurs when parsing a receive (Rx) buffer containing TLV (Type-Length-Value) payload data. The vulnerability likely stems from insufficient bounds checking during TLV parsing, allowing an attacker to corrupt memory via specially crafted wireless frames.
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 the wireless chipset modelCheck system hardware specifications, device manager, or kernel modules for the presence of Qualcomm 315, Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Fastconnect 6200, or Fastconnect 6700 wireless chipsetsAffected if The system uses any of the listed Qualcomm chipset families
-
Determine the firmware versionQuery the wireless device firmware version through vendor-specific tools (such as 'iw', 'ethtool', or chipset-specific diagnostic utilities), or check firmware file metadata if accessibleAffected if The firmware version cannot be determined or is present but unpatched (all versions listed are affected)
-
Verify WLAN HAL is activeCheck if the Wireless LAN Hardware Abstraction Layer module or service is loaded and running. This may be visible in system process lists, kernel module listings ('lsmod'), or service status commands depending on the OSAffected if WLAN HAL is loaded and actively processing wireless frames
-
Confirm wireless receive functionality is enabledVerify that the wireless interface is in monitor or promiscuous mode, or that it actively receives traffic from other devices. Check network interface status and traffic countersAffected if The wireless interface is actively receiving or capable of receiving 802.11 frames containing TLV payloads
A system is affected if it runs any of the listed Qualcomm firmware variants with WLAN HAL enabled and the ability to process incoming wireless Rx frames containing TLV data.
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 dataObtain and apply the vendor-specific patch for the affected wireless driver/HAL implementation. Until a patch is available, consider network segmentation to limit exposure to untrusted wireless traffic.
- Consultation2.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,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28549 — 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-28549 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