CVE-2022-40535
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 due to buffer over-read in WLAN while sending a packet to device.
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 confidenceBuffer over-read vulnerability in the WLAN component allows remote attackers to cause a transient denial of service by sending specially crafted packets to the device. The vulnerability occurs due to insufficient bounds checking when processing incoming wireless packets, leading 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 the chipset or firmware modelCheck the device specifications, hardware documentation, or system logs to determine if the device uses any of the following Qualcomm chipsets: Csr8811, Ipq8070a, Ipq8071a, Ipq8072a, Ipq8074a, Ipq8076, Ipq8076a, or Ipq8078. This information may be visible in dmesg, boot logs, or the device's FCC ID documentation.Affected if The device contains any of the listed Qualcomm chipset models in the firmware version field.
-
Check if WLAN is enabledVerify whether the wireless network interface is active or configured on the device. This may involve checking if wireless interfaces exist (such as wlan0, wl0, or similar) using commands like 'ip link show', 'iwconfig', or by reviewing the device's network configuration.Affected if WLAN is actively enabled or configured on a device with an affected chipset.
-
Confirm firmware version informationRetrieve the installed firmware version if accessible. This may be found in /proc/version, boot logs, or via vendor-specific diagnostic interfaces. Compare the version string against the affected product list.Affected if The device firmware corresponds to any of the listed Qualcomm products, regardless of version number, since all versions are affected.
-
Assess network exposureDetermine whether the device is connected to untrusted or public wireless networks, or if it can receive wireless traffic from outside your trust boundary.Affected if The device with the affected chipset and enabled WLAN is reachable from untrusted wireless networks.
The environment is affected if any device contains one of the listed Qualcomm WLAN chipsets (Csr8811, Ipq8070a, Ipq8071a, Ipq8072a, Ipq8074a, Ipq8076, Ipq8076a, or Ipq8078) with WLAN functionality enabled, as all versions of these products contain the 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-provided patches for the WLAN driver/firmware. Until the patch is available, consider network segmentation to limit exposure to untrusted wireless networks.
- Consultation4.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40535 — 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-40535 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