CVE-2022-50286

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

State
Published
Severity
7.8 High
Published
Sep 15, 2025
Updated
Aug 5, 2026
Reserved
Sep 15, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • d40e09f701cf7a44e595a558b067b2b4f67fbf87 to before f83391339d8493b9ff24167516aaa5a5e88d8f81Affected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before 6f4200ec76a0d31200c308ec5a71c68df5417004Affected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before 9404839e0c9db5a517ea83c0ca3388b39d105fdfAffected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before d440d6427a5e3a877c1c259b8d2b216ddb65e185Affected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193Affected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before 81b915181c630ee1cffa052e52874fe4e1ba91acAffected
  • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 to before 131294c35ed6f777bd4e79d42af13b5c41bf2775Affected
  • 4.19.270 to before 4.19.271Affected
LinuxLinux
  • 4.20Affected
  • before 4.20Not affected
  • 4.19.271 through 4.19.*Not affected
  • 5.4.229 through 5.4.*Not affected
  • 5.10.163 through 5.10.*Not affected
  • 5.15.87 through 5.15.*Not affected
  • 6.0.18 through 6.0.*Not affected
  • 6.1.4 through 6.1.*Not affected
  • 6.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.