CVE-2026-89830
In the Linux kernel, the following vulnerability has been resolved: …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/0f9af07ecc1ab486038373db6ae0436c5d674b19
- git.kernel.org/stable/c/2d50b6d47e5671ff6a25834c5906d443356191f0
- git.kernel.org/stable/c/931e1aa4d44c52ff8e0feb38420a8827c62e886b
- git.kernel.org/stable/c/dde99df5a9d3b0ca6ac0a86f98799685f7399432
- nvd.nist.gov/vuln/detail/CVE-2026-89830
- cve.org/CVERecord?id=CVE-2026-89830
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.