f2fs: accurately adjust free_sections during free_segment_range
- 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.6.160, 6.12.112, 6.18.53, 7.2.7
- 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: f2fs: accurately adjust free_sections during free_segment_range In free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs` to restrict block allocation to the safe remaining main area while valid blocks in the truncated range are evacuated by GC. However, FREE_I(sbi)->free_sections tracks the total number of free sections across the whole filesystem. If any sections within the truncated range were already free upon entering free_segment_range(), failing to deduct them from free_sections causes the filesystem to overestimate available free sections in the active, reduced main area. This leads to inconsistent free section accounting during GC data migration and can trigger unexpected allocation failures or assertion errors when space is tight. Fix this by calculating the number of already-free sections in the truncated range, deducting them from free_sections upon entering free_segment_range(), and restoring them on exit.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b4b10061ef98c583bcf82a4200703fbaa98c18dc · fixed in 64a7ed42e9766886dd7300597d90366dfb7a1e53; From b4b10061ef98c583bcf82a4200703fbaa98c18dc · fixed in faeb0a20bdd113311519b598dcc075af3b6fb366; From b4b10061ef98c583bcf82a4200703fbaa98c18dc · fixed in ca31116fad0954c61a0d38163cc51c48e4981b75; From b4b10061ef98c583bcf82a4200703fbaa98c18dc · fixed in 8a123a10770d2132d046748f20f02baa8d5539a1; From b4b10061ef98c583bcf82a4200703fbaa98c18dc · fixed in 8c963d1738fdca400082ff5f9d99e083de4f4e70
- Linux Linux
5.8
- KernelLinux
From 5.8.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7