Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97534f2fs: accurately adjust free_sections during free_segment_range

Description

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

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 35 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 9e7a744c9db8c2d33ed6ac2ff9bca9323a38b038
    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 64a7ed42e9766886dd7300597d90366dfb7a1e53
    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < faeb0a20bdd113311519b598dcc075af3b6fb366
    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < ca31116fad0954c61a0d38163cc51c48e4981b75
    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 8a123a10770d2132d046748f20f02baa8d5539a1
    • affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 8c963d1738fdca400082ff5f9d99e083de4f4e70
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97534 badge
[![CVE-2026-97534](https://cveledger.app/badge/CVE-2026-97534.svg)](https://cveledger.app/cve/CVE-2026-97534)

Record last updated .