CVE-2022-40512
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 in WLAN Firmware due to buffer over-read while processing probe response or beacon.
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 buffer over-read vulnerability in WLAN firmware allows specially crafted probe response or beacon frames to trigger a denial of service. The vulnerability exists in the wireless frame parsing logic, where insufficient bounds checking during processing of these management frames leads to reading beyond allocated buffer boundaries.
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 WLAN hardware componentRun commands such as 'lspci | grep -i wireless', 'lspci | grep -i wifi', 'iw dev', or check /proc/bus/pci/devices to enumerate wireless network adapters. On Android, check 'settings > about phone > baseband' or use 'getprop' commands.Affected if The device uses a Qualcomm Atheros or other wireless chipset that matches the affected models (Apq8009, Apq8017, Apq8064au, Apq8076, Apq8092, Apq8094, Apq8096au, Aqt1000).
-
Retrieve WLAN firmware versionUse firmware extraction tools or system information utilities. On Linux: 'cat /sys/class/net/*/device/firmware_version' or check 'dmesg | grep -i firmware' for boot-time firmware loading messages. On embedded systems, check vendor-specific diagnostic interfaces or debug logs.Affected if The firmware version cannot be determined to be patched OR the firmware is present on an affected chipset listed in the CVE (all versions of Apq8009, Apq8017, Apq8064au, Apq8076, Apq8092, Apq8094, Apq8096au, Aqt1000 are vulnerable).
-
Verify wireless interface statusRun 'ip link show' or 'ifconfig -a' to list network interfaces. Check for active wireless interfaces (typically named wlan0, wlp*, or similar). Use 'iw dev <interface> info' to confirm the interface is up.Affected if A wireless interface is present and in an UP or UP-like state, meaning the device is actively processing wireless frames including probe responses and beacons.
-
Check for management frame processingVerify the wireless card is not in monitor/flight mode. Run 'rfkill list' to check if wireless is blocked. Use 'iw dev' to confirm the interface is in managed mode (normal client operation) rather than completely disabled.Affected if Wireless is operational and not fully disabled - the device will process incoming probe response and beacon frames from access points, which is the attack vector for this CVE.
If the system contains any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8064au, Apq8076, Apq8092, Apq8094, Apq8096au, Aqt1000) with active wireless functionality, the device 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-supplied firmware updates for affected WLAN devices. In the interim, consider disabling wireless interfaces in critical systems or implementing network access controls to limit exposure to unauthenticated wireless frame injection.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40512 — 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-2022-40512 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