Answer in brief
CVE-2026-97534 records a Unknown severity vulnerability in f2fs: accurately adjust free_sections during free_segment_range. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b4b10061ef98c583bcf82a4200703fbaa98c18dc <ca31116fad0954c61a0d38163cc51c48e4981b75 || >=b4b10061ef98c583bcf82a4200703fbaa98c18dc <8a123a10770d2132d046748f20f02baa8d5539a1 || >=b4b10061ef98c583bcf82a4200703fbaa98c18dc <8c963d1738fdca400082ff5f9d99e083de4f4e70 | ca31116fad0954c61a0d38163cc51c48e4981b75, 8a123a10770d2132d046748f20f02baa8d5539a1, 8c963d1738fdca400082ff5f9d99e083de4f4e70 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.