dbcve.org
Linux KernelOperating system · Linux

CVE-2022-50022

HIGH · 7.8 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 4.9.326 / 4.14.291 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
In the Linux kernel, the following vulnerability has been resolved: drivers:md:fix a potential use-after-free bug In line 2884, "raid5_release_stripe(sh);" drops the reference to sh and may cause sh to be released. However, sh is subsequently used in lines 2886 "if (sh->batch_head && sh != sh->batch_head)". This may result in an use-after-free bug. It can be fixed by moving "raid5_release_stripe(sh);" to the bottom of the function.

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-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free 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:>= 4.1, < 4.9.326>= 4.10, < 4.14.291>= 4.15, < 4.19.256>= 4.20, < 5.4.211>= 5.5, < 5.10.138>= 5.11, < 5.15.63>= 5.16, < 5.19.4

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 4.9.326 / 4.14.291 / 4.19.256 or later
Fixed in 4.9.3264.14.2914.19.256
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 4.9.326+ (4.9.x branch), 4.14.291+ (4.14.x branch), 4.19.256+ (4.19.x branch), or 5.4.211+ (5.4.x branch). Newer stable branches (5.10.x, 6.x) also include this fix.

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Check which major kernel branch your system is on (e.g., 4.9.x, 4.14.x, 4.19.x, 5.4.x)
  3. 3. For 4.9.x branch: upgrade to kernel version 4.9.326 or later
  4. 4. For 4.14.x branch: upgrade to kernel version 4.14.291 or later
  5. 5. For 4.19.x branch: upgrade to kernel version 4.19.256 or later
  6. 6. For 5.4.x branch: upgrade to kernel version 5.4.211 or later
  7. 7. For newer branches (5.10.x, 6.x): ensure the stable patch 09cf99bace7789d91caa8d10fbcfc8b2fb35857f is included in your kernel version
  8. 8. After upgrade, reboot the system to load the fixed kernel
Caveat Kernel upgrades may require rebuilding third-party kernel modules. Ensure compatibility of critical drivers/modules with the new kernel version before production deployment.

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-50022 — 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-50022 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