CVE-2022-34146
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 improper input validation in WLAN Host while parsing frame during defragmentation.
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 denial of service vulnerability exists in the WLAN host driver where improper input validation occurs during the parsing of wireless frames during the defragmentation process. An attacker can exploit this by sending specially crafted fragmented frames that trigger the parsing logic to fail, causing a transient denial of service condition.
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 wireless chipset modelCheck the device's hardware specifications or use commands like 'lspci', 'iw list', 'cat /proc/cpuinfo', or check the bootloader/uboot configuration to identify the Qualcomm wireless chipset (Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, Ipq6018, or Ipq6028)Affected if The device uses any of the listed Qualcomm chipsets (Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, Ipq6018, Ipq6028)
-
Check the installed firmware versionRetrieve the firmware version from the device's system information, wireless interface diagnostics, or boot logs (commands like 'cat /sys/firmware/devicetree/base/model', 'cat /proc/version', or vendor-specific CLI tools)Affected if The firmware version is any version of the listed Qualcomm chipsets (all versions are affected)
-
Verify wireless interface is activeCheck if wireless interfaces are up using 'ip link show', 'iwconfig', or 'ip addr' to see if wlan0, wlan1, or similar interfaces exist and are in UP stateAffected if Wireless interfaces are enabled and active, as the vulnerability is exploited via incoming fragmented wireless frames
-
Check for wireless fragmentation configurationInspect wireless interface settings using 'iw dev <interface> info' or 'iwlist <interface> frag' to see if fragmentation handling is enabledAffected if Fragmentation support is enabled on the wireless interface, which is required for the defragmentation vulnerability to be triggerable
-
Review system logs for wireless-related crashesExamine kernel logs, system messages, or vendor logs for signs of wireless driver failures, unexpected reboots, or WLAN subsystem crashes (commands like 'dmesg', 'cat /var/log/messages', 'journalctl -k')Affected if Recent unexplained wireless driver crashes, system instability, or unexpected reboots coincide with wireless traffic activity
You are affected if your device uses any of the listed Qualcomm chipsets (Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, Ipq6018, Ipq6028) and has wireless functionality enabled.
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 dataImplement proper input validation and bounds checking on incoming fragmented wireless frames before processing, and add error handling to prevent crashes during the defragmentation process.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34146 — 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-34146 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