{"id":"CVE-2026-97534","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: accurately adjust free_sections during free_segment_range\n\nIn free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs`\nto restrict block allocation t…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: accurately adjust free_sections during free_segment_range\n\nIn free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs`\nto restrict block allocation t…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= b4b10061ef98c583bcf82a4200703fbaa98c18dc < ca31116fad0954c61a0d38163cc51c48e4981b75","Linux >= b4b10061ef98c583bcf82a4200703fbaa98c18dc < 8a123a10770d2132d046748f20f02baa8d5539a1","Linux >= b4b10061ef98c583bcf82a4200703fbaa98c18dc < 8c963d1738fdca400082ff5f9d99e083de4f4e70","Linux 5.8"],"published":"2026-09-25","updated":"2026-09-25","sourceUpdated":"2026-09-25T11:17:03.643","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97534","references":[{"url":"https://git.kernel.org/stable/c/8a123a10770d2132d046748f20f02baa8d5539a1","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/8c963d1738fdca400082ff5f9d99e083de4f4e70","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/ca31116fad0954c61a0d38163cc51c48e4981b75","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-25T11:06:38.923Z","slug":"CVE-2026-97534","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: accurately adjust free_sections during free_segment_range\n\nIn free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs`\nto restrict block allocation to the safe remaining main area while valid\nblocks in the truncated range are evacuated by GC.\n\nHowever, FREE_I(sbi)->free_sections tracks the total number of free\nsections across the whole filesystem. If any sections within the\ntruncated range were already free upon entering free_segment_range(),\nfailing to deduct them from free_sections causes the filesystem to\noverestimate available free sections in the active, reduced main area.\nThis leads to inconsistent free section accounting during GC data\nmigration and can trigger unexpected allocation failures or assertion\nerrors when space is tight.\n\nFix this by calculating the number of already-free sections in the\ntruncated range, deducting them from free_sections upon entering\nfree_segment_range(), and restoring them on exit.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}