f2fs: fix valid block count leak on data block allocation failure (CVE-2026-89830) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89830

f2fs: fix valid block count leak on data block allocation failure

Answer in brief

CVE-2026-89830 records a Unknown severity vulnerability in f2fs: fix valid block count leak on data block allocation failure. 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.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 <2d50b6d47e5671ff6a25834c5906d443356191f0 \|\| >=7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 <dde99df5a9d3b0ca6ac0a86f98799685f7399432 \|\| >=7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 <931e1aa4d44c52ff8e0feb38420a8827c62e886b \|\| >=7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 <0f9af07ecc1ab486038373db6ae0436c5d674b19	2d50b6d47e5671ff6a25834c5906d443356191f0, dde99df5a9d3b0ca6ac0a86f98799685f7399432, 931e1aa4d44c52ff8e0feb38420a8827c62e886b, 0f9af07ecc1ab486038373db6ae0436c5d674b19
Linux/Linuxgeneric	6.9	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 2d50b6d47e5671ff6a25834c5906d443356191f0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix valid block count leak on data block allocation failure In __allocate_data_block(), when allocating a new data block (dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is called first to increment total_valid_block_count and i_blocks. If the subsequent f2fs_allocate_data_block() fails, the function returns the error directly without rolling back the already-incremented block counts, causing a permanent leak. Fix this by calling dec_valid_block_count() to undo the increment before returning the error. The condition old_blkaddr == NULL_ADDR precisely identifies the case where inc_valid_block_count() was called.

Quoted source text, attributed separately from HOL analysis.