dbcve.org
Linux KernelOperating system · Linux

CVE-2022-47521

HIGH · 7.8 CVSS v3.1 Published 2022-12-18
Fix available
A fix is available. Upgrade to 5.10.157 / 5.15.81 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 · unedited
An issue was discovered in the Linux kernel before 6.0.11. Missing validation of IEEE80211_P2P_ATTR_CHANNEL_LIST in drivers/net/wireless/microchip/wilc1000/cfg80211.c in the WILC1000 wireless driver can trigger a heap-based buffer overflow when parsing the operating channel attribute from Wi-Fi management frames.

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
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 data
Linux KernelOperating system
Affected:>= 5.7, < 5.10.157>= 5.11, < 5.15.81>= 5.16, < 6.0.11
Debian LinuxOperating system
Affected:= 10.0
H410c FirmwareOperating system
Affected:all versions
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H410s FirmwareOperating system
Affected:all versions

CVSS 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

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.

dbcve · scoped
Upgrade available Upgrade to 5.10.157 / 5.15.81 / 6.0.11 or later
Fixed in 5.10.1575.15.816.0.11
Vendor patch github.com →
Recommended fix High confidence

Linux kernel 5.10.157+/5.15.81+/6.0.11+ (recommended: 6.1.x stable or later)

  1. Identify current kernel version using 'uname -r' or 'cat /proc/version'
  2. For kernel 5.10.x branch: upgrade to 5.10.157 or later (recommended: 5.10.158 or later)
  3. For kernel 5.11-5.15.x branch: upgrade to 5.15.81 or later (recommended: 5.15.128 or later)
  4. For kernel 5.16-6.0.x branch: upgrade to 6.0.11 or later (recommended: 6.1.x stable or later)
  5. On Debian 10 systems: run 'apt-get update && apt-get dist-upgrade' to get kernel 5.10.158+ from buster-updates, or upgrade to Debian 11/12
  6. For embedded devices (H410c, H300s, H500s, H700s, H410s): contact Microchip for firmware updates containing the kernel fix
  7. Reboot into the new kernel and verify version with 'uname -r'
Caveat Kernel upgrades may require rebuilding third-party kernel modules (e.g., proprietary drivers like NVIDIA, VirtualBox). Ensure compatibility with new kernel before rebooting. On Debian, may need to hold or adjust package preferences if mixing releases.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47521 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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