CVE-2026-63817

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FSCOMPRESSINO uses NMIsbi-maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compresscache mount option is enabled. Wh...

EUVD-2026-45483

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FSCOMPRESSINO uses NMIsbi-maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compresscache mount option is enabled. Wh...

CVE-2026-63817 f2fs: validate compress cache inode only when enabled

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FSCOMPRESSINO uses NMIsbi-maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compresscache mount option is enabled. Wh...

CVE-2026-63817

The CVE-2026-63817 issue pertains to the Linux kernel file system F2FS: when the compress_cache mount option is enabled, F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode for the compressed page cache inode. If compress_cache is disabled, max_nid lies outside the valid inode r...

CVE-2026-63817

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FSCOMPRESSINO uses NMIsbi-maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compresscache mount option is enabled. Wh...

CVE-2026-63813

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in movedatablock" This reverts commit 9609dd704725a40cd63d915f2ab6c44248a44598. The kernel panics are keeping to be reported especially when the f2fs partition get almos...

EUVD-2026-45479

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in movedatablock" This reverts commit 9609dd704725a40cd63d915f2ab6c44248a44598. The kernel panics are keeping to be reported especially when the f2fs partition get almos...

CVE-2026-63813

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in movedatablock" This reverts commit 9609dd704725a40cd63d915f2ab6c44248a44598. The kernel panics are keeping to be reported especially when the f2fs partition get almos...

CVE-2026-63813

Summary: CVE-2026-63813 relates to the Linux kernel and a revert of a previous f2fs change in move_data_block that could cause page-cache/folio handling race conditions. The embedded details describe a race where the GC path can evict the tail-end folio from the page cache, drop page-cache refere...

CVE-2026-63813 Revert "f2fs: remove non-uptodate folio from the page cache in move_data_block"

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in movedatablock" This reverts commit 9609dd704725a40cd63d915f2ab6c44248a44598. The kernel panics are keeping to be reported especially when the f2fs partition get almos...

CVE-2026-63813 Revert "f2fs: remove non-uptodate folio from the page cache in move_data_block"

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in movedatablock" This reverts commit 9609dd704725a40cd63d915f2ab6c44248a44598. The kernel panics are keeping to be reported especially when the f2fs partition get almos...

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-53388

CVE-2026-53388 : Linux kernel fuse module vulnerability where fuse_try_move_folio() unlocks the request on entry but does not re-lock on the success path, allowing a use-after-free of fuse_io_args via fuse_chan_abort() and delayed copying logic. The issue is resolved by calling lock_request() bef...

CVE-2026-53388

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymovefolio unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort can end the request and free the fuseioargs eg...

EUVD-2026-45510

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymovefolio unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort can end the request and free the fuseioargs eg...

CVE-2026-53388 fuse: re-lock request before replacing page cache folio

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymovefolio unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort can end the request and free the fuseioargs eg...

CVE-2026-53388 fuse: re-lock request before replacing page cache folio

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymovefolio unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort can end the request and free the fuseioargs eg...

CVE-2026-53388

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymovefolio unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort can end the request and free the fuseioargs eg...