ext4: fix transaction overflow during writeback
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.17, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: fix transaction overflow during writeback Commit 95ad8ee45cdb ("ext4: correct the reserved credits for extent conversion") was correct to note that we need to reserve enough credits for all extents possibly underlying a large folio. However it was too eager to reduce the number of reserved credits. Extent conversion may not only need to touch several leaf extent blocks, it may also need to split extents - for example a single large unwritten extent may need to be split into many small written ones in case of sparse folio dirtying. This can thus result not only in extent leaf modifications but also in a need to allocate new extent tree nodes. As a result the reserved transaction credits were not sufficient in some corner cases. Use ext4_meta_trans_blocks() for correct upper bound credit estimate.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 95ad8ee45cdbc321c135a2db895d48b374ef0f87 · fixed in a22464c5df5827e884a5a7d3d8fb03870e5bb6c8; From 95ad8ee45cdbc321c135a2db895d48b374ef0f87 · fixed in 46e8e31771f4f1c5e1cdec37a889a6730e42e9f1; From 6.16.3 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 7.2.6