CVE-2022-50286

ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline

MEDIUM
5.5
CVSS Score
Published: September 15, 2025 at 02:21 PM UTC
Updated: August 5, 2026 at 09:24 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
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline When converting files with inline data to extents, delayed allocations made on a file system created with both the bigalloc and inline options can result in invalid extent status cache content, incorrect reserved cluster counts, kernel memory leaks, and potential kernel panics. With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if that block maps to a previously allocated cluster. If not, the block is delayed allocated, and otherwise, it isn't. However, if the inline option is also used, and if the file containing the block is marked as able to store data inline, there isn't a valid extent tree associated with the file. The current code in ext4_clu_mapped() calls ext4_find_extent() to search the non-existent tree for a previously allocated cluster anyway, which typically finds nothing, as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) in the extent status tree, including bogus entries in the pending reservation tree. To fix this, avoid searching the extent tree when allocating blocks for bigalloc + inline files that are being converted from inline to extent mapped.

Affected

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

v < 5.4.2294.19.270 ≤ v < 4.19.2714.20 ≤ v < 5.10.1634.20 ≤ v < 5.15.874.20 ≤ v < 5.4.2294.20 ≤ v < 6.0.184.20 ≤ v < 6.1.44.20 ≤ v < 6.25.11 ≤ v < 5.15.875.16 ≤ v < 6.0.185.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.40b02f4c0d6d9e2c611dfbdd4317193e9dca740e64.19.2704.20d40e09f701cf7a44e595a558b067b2b4f67fbf87
Vendor states this is fixed in 131294c35ed6f777bd4e79d42af13b5c41bf2775 (fixed)
Vendor states this is fixed in 6f4200ec76a0d31200c308ec5a71c68df5417004 (fixed)
Vendor states this is fixed in 81b915181c630ee1cffa052e52874fe4e1ba91ac (fixed)
Vendor states this is fixed in 9404839e0c9db5a517ea83c0ca3388b39d105fdf (fixed)
Vendor states this is fixed in c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193 (fixed)
Vendor states this is fixed in d440d6427a5e3a877c1c259b8d2b216ddb65e185 (fixed)
Vendor states this is fixed in f83391339d8493b9ff24167516aaa5a5e88d8f81 (fixed)
Vendor states this is fixed in 4.19.271 (unaffected)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.87 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.18 (unaffected)
Vendor states this is fixed in 6.1.4 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card