CVE-2023-28565
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 handling command streams through WMI interfaces.
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 occurs when processing command streams through WMI (Wireless Management Interface) interfaces, potentially allowing local attackers to execute arbitrary code or cause denial of service via specially crafted wireless commands.
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 Qualcomm chipset modelCheck the device hardware specifications or system information to determine if the WLAN adapter uses one of the affected Qualcomm chipsets: 9205 LTE, Apq8017, Apq8064au, Apq8076, Apq8092, Apq8094, Aqt1000, or Ar7420Affected if The device contains any of the listed Qualcomm chipset models
-
Verify WLAN/HAL component is presentCheck if the WLAN Hardware Abstraction Layer module is loaded or present on the system - this may be visible in system modules, driver lists, or hardware enumerationAffected if The WLAN HAL module is present and active on the device
-
Confirm WMI interface availabilityInspect whether the Wireless Management Interface (WMI) is accessible on the system - this interface is required for the attack vectorAffected if The WMI interface is enabled and accessible
-
Determine firmware versionIf accessible, query the WLAN firmware version through system diagnostic tools, driver information, or firmware revision interfacesAffected if The firmware version matches any of the affected Qualcomm firmware types listed (all versions are affected)
If the device uses any of the eight affected Qualcomm chipset models (9205 LTE, Apq8017, Apq8064au, Apq8076, Apq8092, Apq8094, Aqt1000, Ar7420) with WLAN and WMI interface enabled, the environment is affected since all versions of these firmwares are vulnerable.
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 or firmware updates for the affected WLAN driver/HAL component; prioritize patching wireless client and access point devices given the WMI interface involvement.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28565 — 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-28565 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