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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 to < 2d50b6d47e5671ff6a25834c5906d443356191f0affected7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 to < dde99df5a9d3b0ca6ac0a86f98799685f7399432affected7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 to < 931e1aa4d44c52ff8e0feb38420a8827c62e886baffected7d009e048d7cfcc21d400f2aba4c8bacbdebbd47 to < 0f9af07ecc1ab486038373db6ae0436c5d674b19affected
Linux Linux
Default version status: affected
6.9affected0 to < 6.9unaffected6.12.110 to ≤ 6.12.*unaffected6.18.51 to ≤ 6.18.*unaffected7.2.5 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected