ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 · < 81b915181c630ee1cffa052e52874fe4e1ba91ac| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel, converting inline-data files to extents on an ext4 filesystem configured with both bigalloc and inline can corrupt extent status cache entries and reserved cluster counts. An attacker able to trigger this condition could cause kernel memory leaks or a panic; the input does not specify whether network access, authentication, or user interaction is required.
Anyone running the Linux kernel with ext4 filesystems configured with both bigalloc and inline should check their kernel version; affected versions are not specified.