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 NMI(sbi)->maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compresscache mount option is enabled.
When compresscache is disabled, maxnid is outside the valid inode range. A corrupted directory entry that points to ino == maxnid should therefore be rejected by f2fschecknidrange(). However, ismetaino() currently treats F2FSCOMPRESSINO() as a meta inode unconditionally, so f2fsiget() bypasses doreadinode() and its nid range check, and instantiates a fake internal inode instead.
Gate the compressed cache inode case on COMPRESSCACHE, matching f2fsinitcompressinode(). With compresscache disabled, ino == maxnid now follows the normal inode path and is rejected as an out-of-range nid.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63817?
The severity of CVE-2026-63817 is high, with a CVSS score of 7.8.
How do I fix CVE-2026-63817?
To fix CVE-2026-63817, ensure that the Linux kernel is updated to a version that includes the relevant patch.
What systems are affected by CVE-2026-63817?
CVE-2026-63817 affects the Linux kernel specifically when using the F2FS filesystem with the compress_cache mount option enabled.
What types of attacks can result from CVE-2026-63817?
CVE-2026-63817 could potentially allow attackers to exploit vulnerabilities in cached compressed data, leading to unauthorized access or data corruption.
What is the primary cause of CVE-2026-63817?
The primary cause of CVE-2026-63817 is the improper validation of the compress cache inode in the Linux kernel when the option is enabled.