CVE-2026-63812

HighCVSS 7.8/10Last modified Nov 10, 2026

Description

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()

When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the extent tree are disallowed afterward, the cached largest extent may become stale. This can trigger the following error in xfstests generic/388:

F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix

In the f2fs_drop_inode path, __destroy_extent_node() does not need to guarantee that et->node_cnt is 0, because concurrency with writeback is expected in this path, and writeback may update the extent cache.

This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between extent node destroy and writeback"), and remove the unnecessary zero check of et->node_cnt.

Metrics

CVSS 3.1 7.8/10CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness enumeration

Affected software

VendorProductVersions
LinuxLinux>= 42dd1c91f993431d0b399502479d00e6ad1bca71, < 7e4d8f98be63f98856a5176b9188dada6e7ba9ee; >= ab1eaf9d5c99042f5b0243bf67a06283a4c0757f, < 58a5deb220bcac4c73bf58954c0845644c997487; >= b0e4395870eb3441ddc959f6710b5f6ca61aff26, < 20190e498057997532c7f186d081011f18e0a462; >= ed78aeebef05212ef7dca93bd931e4eff67c113f, < edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7; >= ed78aeebef05212ef7dca93bd931e4eff67c113f, < 1f70ddb28a3c71df124da5fa4040c808116d6bb9; b00e6950da9c0e4986f6e93c875d2b9184bdb220; 0559a0e962aacbb47519e26ee663be04b72dcb92; >= 6.6.140, < 6.6.144; >= 6.12.88, < 6.12.95; >= 6.18.30, < 6.18.38; >= 6.1.191, < 6.2; >= 7.0.7, < 7.1
LinuxLinux7.1

References

Timeline

Published
Jul 19, 2026
Last modified
Nov 10, 2026
NVD status
Analyzed

Related CVEs from 2026

CVE-2026-638137.8In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in move_datCVE-2026-638147.8In the Linux kernel, the following vulnerability has been resolved: f2fs: validate ACL entry sizes in f2fs_acl_from_disk() f2fs_acl_count(CVE-2026-638158.4In the Linux kernel, the following vulnerability has been resolved: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes When the fCVE-2026-638167.8In the Linux kernel, the following vulnerability has been resolved: f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode - ioctl(F2CVE-2026-638177.8In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INCVE-2026-638188.4In the Linux kernel, the following vulnerability has been resolved: f2fs: validate orphan inode entry count f2fs_recover_orphan_inodes() tCVE-2026-638197.8In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on f2fs_get_node_folio_ra() kernel BUG atCVE-2026-63829.1The FileOrganizer WordPress plugin before 1.1.9, Advanced File Manager WordPress plugin before 5.4.12, File Manager Pro WordPress plugin CVE-2026-638205.5In the Linux kernel, the following vulnerability has been resolved: f2fs: fix missing read bio submission on large folio error f2fs_read_dCVE-2026-638215.5In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: usb: fix memory leaks on USB write failures When rtw_usb_CVE-2026-638227.8In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix warning when unbinding If there is an error during sCVE-2026-638237.8In the Linux kernel, the following vulnerability has been resolved: keys: Pin request_key_auth payload in instantiate paths A: request_key
CVE-2026-63812: High severity, CVSS 7.8 | Vulnix