CVE-2022-50020

ext4: avoid resizing to a partial cluster size

MEDIUM

5.5

CVSS Score

Published: June 18, 2025 at 11:01 AM UTC

Updated: June 17, 2026 at 05:22 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 4.9.3264.10 ≤ v < 4.14.2914.15 ≤ v < 4.19.2564.15 ≤ v < 5.10.1384.15 ≤ v < 5.15.634.15 ≤ v < 5.19.44.15 ≤ v < 5.4.2114.15 ≤ v < 6.04.20 ≤ v < 5.4.2115.11 ≤ v < 5.15.635.16 ≤ v < 5.19.45.5 ≤ v < 5.10.1384.15d77147ff443b255d82c907a632c825b2cc610b10

Vendor states this is fixed in 0082e99a9074ff88eff729c70c93454c8588d8e1 (fixed)

Vendor states this is fixed in 69cb8e9d8cd97cdf5e293b26d70a9dee3e35e6bd (fixed)

Vendor states this is fixed in 72b850a2a996f72541172e7cf686d54a2b29bcd8 (fixed)

Vendor states this is fixed in 7bdfb01fc5f6b3696728aeb527c50386e0ee09a1 (fixed)

Vendor states this is fixed in 80288883294c5b4ed18bae0d8bd9c4a12f297074 (fixed)

Vendor states this is fixed in a6805b3dcf5cd41f2ae3a03dca43411135b99849 (fixed)

Vendor states this is fixed in 4.15 (unaffected)

Vendor states this is fixed in 4.19.256 (unaffected)

Vendor states this is fixed in 5.10.138 (unaffected)

Vendor states this is fixed in 5.15.63 (unaffected)

Vendor states this is fixed in 5.19.4 (unaffected)

Vendor states this is fixed in 5.4.211 (unaffected)