CVE-2026-89830

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.

CVSS

No CVSS.

References

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

Configurations

No configuration.

History

No history.

Information

Published : 2026-09-16 11:16

Updated : 2026-09-16 11:16

NVD link : CVE-2026-89830

Mitre link : CVE-2026-89830

CVE.ORG link : CVE-2026-89830

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-89830", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "7d009e048d7cfcc21d400f2aba4c8bacbdebbd47", "lessThan": "2d50b6d47e5671ff6a25834c5906d443356191f0", "versionType": "git"}, {"status": "affected", "version": "7d009e048d7cfcc21d400f2aba4c8bacbdebbd47", "lessThan": "dde99df5a9d3b0ca6ac0a86f98799685f7399432", "versionType": "git"}, {"status": "affected", "version": "7d009e048d7cfcc21d400f2aba4c8bacbdebbd47", "lessThan": "931e1aa4d44c52ff8e0feb38420a8827c62e886b", "versionType": "git"}, {"status": "affected", "version": "7d009e048d7cfcc21d400f2aba4c8bacbdebbd47", "lessThan": "0f9af07ecc1ab486038373db6ae0436c5d674b19", "versionType": "git"}], "programFiles": ["fs/f2fs/data.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.9"}, {"status": "unaffected", "version": "0", "lessThan": "6.9", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.110", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.51", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.5", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["fs/f2fs/data.c"], "defaultStatus": "affected"}]}], "published": "2026-09-16T11:16:49.753", "references": [{"url": "https://git.kernel.org/stable/c/0f9af07ecc1ab486038373db6ae0436c5d674b19", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/2d50b6d47e5671ff6a25834c5906d443356191f0", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/931e1aa4d44c52ff8e0feb38420a8827c62e886b", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/dde99df5a9d3b0ca6ac0a86f98799685f7399432", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix valid block count leak on data block allocation failure\n\nIn __allocate_data_block(), when allocating a new data block\n(dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is\ncalled first to increment total_valid_block_count and i_blocks.\nIf the subsequent f2fs_allocate_data_block() fails, the function\nreturns the error directly without rolling back the\nalready-incremented block counts, causing a permanent leak.\n\nFix this by calling dec_valid_block_count() to undo the\nincrement before returning the error. The condition\nold_blkaddr == NULL_ADDR precisely identifies the case where\ninc_valid_block_count() was called."}], "lastModified": "2026-09-16T11:16:49.753", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}