CVE-2022-25667
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 · uneditedInformation disclosure in kernel due to improper handling of ICMP requests in 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 · high confidenceA kernel-level information disclosure vulnerability exists in Snapdragon Wired Infrastructure and Networking components due to improper handling of ICMP requests. The flaw allows unauthorized disclosure of sensitive kernel memory information through specially crafted ICMP packets.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 device model and chipsetCheck the device documentation, label, or system information to determine if the hardware uses a Qualcomm Snapdragon Wired Infrastructure or Networking chipset (Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, Ipq5010, or Ipq5018)Affected if The device contains any of the listed Qualcomm chipsets (Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, Ipq5010, or Ipq5018)
-
Determine the firmware versionAccess the device firmware or bootloader interface and retrieve the firmware version string. On many embedded devices, this is available via the administrative web interface under 'Status' or 'Firmware Information', or via command line using 'cat /proc/version' or 'uname -a' if shell access is availableAffected if The firmware version matches any of the listed affected products (Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, Ipq5010, or Ipq5018) regardless of version number, as all versions are affected
-
Verify ICMP handling is accessibleFrom an external host, attempt to send ICMP echo requests (ping) to the affected device IP address. Check if the device responds to ICMP packets on any interfaceAffected if The device responds to ICMP echo requests, as the vulnerability is triggered through specially crafted ICMP packets
-
Confirm kernel memory exposure potentialAnalyze any ICMP echo responses received from the device using packet capture tools (such as tcpdump or Wireshark) to examine if response contents contain unexpected data patterns that could indicate kernel memory disclosureAffected if ICMP responses contain anomalous data patterns or information not expected in standard echo replies, suggesting potential kernel memory disclosure
A system is affected if it runs any of the listed Qualcomm chipset firmware (Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, Ipq5010, or Ipq5018) and processes ICMP requests, since all versions of these products are vulnerable to kernel memory disclosure through ICMP.
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 firmware updates for Snapdragon Wired Infrastructure and Networking products; until patches are available, network segmentation may reduce attack surface but cannot fully mitigate the kernel-level flaw.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25667 — 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-25667 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