LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50022: drivers:md:fix a potential use-after-free bug

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50022 is a Linux kernel bug in the md RAID5 driver. A reference to an internal stripe object can be released before later code still uses it, creating a potential use-after-free. The public record does not provide CVSS, CWE, exploitability, or active exploitation evidence.

Executive priority

Handle through the normal kernel vulnerability patch process, with higher priority for business-critical Linux storage systems using md RAID5. There is no sourced evidence of active exploitation, but the impact area is kernel storage code, so delay should be justified and tracked.

Technical view

The issue is in Linux kernel drivers/md RAID5 handling. raid5_release_stripe(sh) may drop the final reference to sh, but subsequent logic checks sh->batch_head. The documented fix moves raid5_release_stripe(sh) to the bottom of the function so sh is not used after possible release.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with md RAID5 code in use. The source lists multiple Linux kernel version lines as affected, but does not map them to distribution packages, appliances, cloud images, or specific configurations.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit code, or a remote attack path. Treat exploitability as not established from the available sources, while still recognizing kernel use-after-free bugs can be security-relevant.

Researcher notes

The record is narrowly scoped to a lifetime bug in RAID5 stripe handling. The affected-version data is sparse and commit-oriented, so validation should rely on kernel source or vendor backport confirmation rather than version strings alone.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fix commits.
  • Check Linux distribution advisories for the corrected package for your kernel line.
  • Prioritize storage hosts using md RAID5 or related md functionality.
  • Avoid inventing workarounds; follow vendor kernel guidance if patching is delayed.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems using md RAID5 or loading the relevant md RAID5 driver path.
  • Confirm the kernel package includes one of the referenced stable commits.
  • Review vendor changelogs or advisories for CVE-2022-50022 coverage.
  • Monitor stability logs for storage or kernel faults during rollout.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c, 59fc630b8b5f9f21c8ce3ba153341c107dce1b0cunaffected
LinuxLinux4.1, 0, 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.