CVE-2022-40522
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 · uneditedMemory corruption in Linux Networking due to double free while handling a hyp-assign.
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 double-free vulnerability exists in the Linux kernel's networking subsystem when handling hypervisor resource assignment ('hyp-assign'). This memory corruption bug allows a double free of a network buffer or object, potentially leading to heap corruption and possible privilege escalation in virtualized environments.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Qualcomm firmware in useCheck the device or system information to determine which Qualcomm chip and firmware version is running (e.g., via 'cat /proc/version', device sysfs, or firmware banner)Affected if The firmware matches any of the affected products: Csr8811, Wcn3991, Wcn3998, Ipq6000, Ipq6005, Ipq6010, Ipq6018, or Ipq6028
-
Verify hypervisor assignment feature is enabledCheck if the 'hyp-assign' or hypervisor resource assignment feature for network devices is actively enabled in the kernel configuration or runtime environmentAffected if The hypervisor assignment feature for network resources is enabled and in use
-
Confirm virtualized environment is in useDetermine whether the system is running in a virtualized environment (e.g., check for hypervisor signatures in /proc/cpuinfo or dmesg)Affected if The affected system operates in a virtualized environment where hypervisor resources can be assigned to guests
-
Inspect kernel logs for double-free indicatorsReview kernel logs (dmesg, /var/log/kern.log) for error messages indicating double-free, heap corruption, or memory corruption related to network buffer handlingAffected if Kernel logs show double-free errors or heap corruption messages in the networking subsystem
A defender is affected if the system runs any of the listed Qualcomm firmware versions AND uses the hypervisor resource assignment feature in a virtualized environment.
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 kernel security updates specific to this CVE. If patches are unavailable, consider restricting or disabling hypervisor assignment features in affected systems until patches are released.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40522 — 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-40522 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