VulnerabilityPublished 25 Sep 2026Updated 21 Oct 2026

CVE-2026-97534: Linux kernel · f2fs: accurately adjust free_sections during free_segment_range

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in faeb0a20bdd113311519b598dcc075af3b6fb366 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in faeb0a20bdd113311519b598dcc075af3b6fb366, ca31116fad0954c61a0d38163cc51c48e4981b75, 64a7ed42e9766886dd7300597d90366dfb7a1e53 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b4b10061ef98c583bcf82a4200703fbaa98c18dc, < faeb0a20bdd113311519b598dcc075af3b6fb366	Fixed in faeb0a20bdd113311519b598dcc075af3b6fb366
LinuxLinux	Affected ≥ b4b10061ef98c583bcf82a4200703fbaa98c18dc, < ca31116fad0954c61a0d38163cc51c48e4981b75	Fixed in ca31116fad0954c61a0d38163cc51c48e4981b75
LinuxLinux	Affected ≥ b4b10061ef98c583bcf82a4200703fbaa98c18dc, < 64a7ed42e9766886dd7300597d90366dfb7a1e53	Fixed in 64a7ed42e9766886dd7300597d90366dfb7a1e53
LinuxLinux	Affected ≥ b4b10061ef98c583bcf82a4200703fbaa98c18dc, < 8c963d1738fdca400082ff5f9d99e083de4f4e70	Fixed in 8c963d1738fdca400082ff5f9d99e083de4f4e70
LinuxLinux	Affected ≥ b4b10061ef98c583bcf82a4200703fbaa98c18dc, < 8a123a10770d2132d046748f20f02baa8d5539a1	Fixed in 8a123a10770d2132d046748f20f02baa8d5539a1
LinuxLinux	Affected =5.8	Fixed in–

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.

References

Community reviews

Loading reviews…