SUSE CVE-2026-63812

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FINOEXTENT handling in destroyextentnode When destroyextentnode sets the inode flag FINOEXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the...

CVE-2026-63812

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FINOEXTENT handling in destroyextentnode When destroyextentnode sets the inode flag FINOEXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the...

EUVD-2026-45478

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FINOEXTENT handling in destroyextentnode When destroyextentnode sets the inode flag FINOEXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the...

CVE-2026-63812 f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FINOEXTENT handling in destroyextentnode When destroyextentnode sets the inode flag FINOEXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the...

CVE-2026-63812

The CVE describes a Linux kernel f2fs bug: when __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it fails to reset the length of the largest extent and update the inode folio, causing a stale cached extent and an error seen in xfstests generic/388. The issue arises in the f2fs_drop_inode...

PT-2026-61128

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the f2fs file system within the destroy extent node function. When the FI NO EXTENT inode flag is set, the system fails to reset the length of the largest extent to 0...