CVE-2022-33237
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 firmware while processing PPE threshold. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
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 Qualcomm Snapdragon WLAN firmware allows an attacker to cause a transient Denial of Service by sending specially crafted packets that trigger the over-read while processing PPE (likely Power Planning Element) threshold data. The vulnerability resides in the firmware layer, not the host operating system.
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 Qualcomm WLAN hardware in useExamine network adapters, WiFi cards, or embedded wireless modules to determine if they contain any of the affected Qualcomm chip families: Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024. This can be done via lspci, lsusb, device datasheets, or hardware inspection.Affected if Any device using one of these specific Qualcomm WLAN chip families is potentially affected since all firmware versions are vulnerable.
-
Determine firmware version of the WLAN chipAccess the device management interface, diagnostic logs, or firmware dump utility provided by the device OEM to retrieve the current WLAN firmware version. For some devices, this may be visible in boot logs, /proc filesystem, or vendor-specific management tools.Affected if The installed firmware version corresponds to any of the listed affected products, regardless of version number, as all versions are vulnerable.
-
Verify if PPE threshold processing is enabledInspect the WLAN firmware configuration or device settings to determine if processing of PPE (Power Planning Element) threshold data is active. This may require access to advanced diagnostic modes or firmware debug interfaces.Affected if The WLAN interface has PPE threshold processing capability enabled and is processing threshold data, which is the trigger condition for the buffer over-read.
-
Assess network exposure of the WLAN interfaceEvaluate whether the affected WLAN interface is directly accessible to unauthenticated attackers. Check if the interface is in bridge mode, monitor mode, or exposed to untrusted network segments.Affected if The vulnerable WLAN interface is network-accessible to untrusted users who could send specially crafted packets to trigger the buffer over-read.
You are affected if your environment contains any device running one of the listed Qualcomm WLAN firmware variants, as all versions are vulnerable and the attack vector involves network-accessible WLAN interfaces processing PPE threshold 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 dataApply firmware updates provided by the device OEM that address this vulnerability in the Snapdragon WLAN component. Until patches are available, network segmentation may limit exposure to unauthenticated WLAN attackers.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33237 — 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-33237 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