CVE-2026-63812

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()<br /> <br /> When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does<br /> not reset the length of the largest extent to 0 and update the inode<br /> folio. Since modifications to the extent tree are disallowed afterward,<br /> the cached largest extent may become stale. This can trigger the<br /> following error in xfstests generic/388:<br /> <br /> F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix<br /> <br /> In the f2fs_drop_inode path, __destroy_extent_node() does not need to<br /> guarantee that et-&gt;node_cnt is 0, because concurrency with writeback<br /> is expected in this path, and writeback may update the extent cache.<br /> <br /> This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between<br /> extent node destroy and writeback"), and remove the unnecessary zero<br /> check of et-&gt;node_cnt.