LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50020: ext4: avoid resizing to a partial cluster size

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel ext4 flaw can break an online filesystem resize when the requested size does not align to the filesystem cluster size. The reported impact is a kernel BUG_ON and corrupted in-memory superblock, which can disrupt systems during storage operations.

Executive priority

Prioritize for Linux servers where storage resizing is routine or automated. This is not evidenced as internet-exploitable, but failures during filesystem maintenance can cause outages and operational recovery work.

Technical view

The ext4 online resize path allowed resizing to a partial cluster boundary. In the final growth iteration, ext4 could attempt a negative filesystem growth amount, trigger BUG_ON, and leave the in-memory superblock corrupted.

Likely exposure

Exposure is most likely on Linux systems using ext4 online resize, especially filesystems with cluster-size alignment requirements, running affected kernel versions listed in the CVE record.

Exploitation context

The bundle does not show KEV listing, public exploitation, remote attack evidence, or exploit maturity. The trigger appears tied to an online resize operation, which usually requires administrative storage control.

Researcher notes

Evidence is limited to the CVE description and kernel stable references. No CVSS, CWE, exploit evidence, or vendor package matrix is included, so validation should focus on kernel provenance and ext4 resize behavior.

Mitigation direction

  • Apply vendor kernel updates containing the referenced ext4 stable fixes.
  • Avoid ext4 online resize requests that end on partial cluster boundaries.
  • Use vendor guidance for exact fixed kernel packages and backports.
  • Treat storage resize operations as change-controlled maintenance until patched.

Validation and detection

  • Inventory Linux systems using ext4 and online resize workflows.
  • Check running kernel versions against vendor advisories and the CVE affected ranges.
  • Review recent storage resize incidents for kernel BUG_ON or ext4 resize errors.
  • Confirm patched kernels include the referenced ext4 resize fix commits.
Prepared
Confidence
medium
Sources
8

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-50020 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
7Source 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
LinuxLinuxd77147ff443b255d82c907a632c825b2cc610b10, d77147ff443b255d82c907a632c825b2cc610b10, d77147ff443b255d82c907a632c825b2cc610b10, d77147ff443b255d82c907a632c825b2cc610b10, d77147ff443b255d82c907a632c825b2cc610b10, d77147ff443b255d82c907a632c825b2cc610b10unaffected
LinuxLinux4.15, 0, 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.