In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INO() uses… (CVE-2026-63817)
In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. A corrupted directory entry that points to ino == max_nid should therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino() currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally, so f2fs_iget() bypasses do_read_inode() and its nid range check, and instantiates a fake internal inode instead. Gate the compressed cache inode case on COMPRESS_CACHE, matching f2fs_init_compress_inode(). With compress_cache disabled, ino == max_nid now follows the normal inode path and is rejected as an out-of-range nid.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's f2fs filesystem relates to the handling of the compressed cache inode number (F2FS_COMPRESS_INO()). This inode number uses max_nid as a synthetic inode number, which only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. However, due to is_meta_ino() treating F2FS_COMPRESS_INO() as a meta inode unconditionally, the inode range check in do_read_inode() was bypassed, allowing f2fs_iget() to instantiate a fake internal inode. The patch corrects this by gating the compressed cache inode case on the compress_cache option, so that with compression disabled, out-of-range inode numbers are rejected normally.
Potential Impact
This vulnerability could allow a corrupted directory entry with an out-of-range inode number to bypass inode validation checks, potentially leading to the instantiation of a fake internal inode within the kernel's f2fs filesystem. This could cause undefined behavior or memory corruption within the kernel, impacting system stability or security. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly gate the compressed cache inode validation on the compress_cache mount option. Users should update their Linux kernel to a version that includes this fix once available. Patch status is not yet confirmed from the vendor advisory; check the official Linux kernel release notes or vendor advisories for the specific fixed version and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INO() uses… (CVE-2026-63817)
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. A corrupted directory entry that points to ino == max_nid should therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino() currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally, so f2fs_iget() bypasses do_read_inode() and its nid range check, and instantiates a fake internal inode instead. Gate the compressed cache inode case on COMPRESS_CACHE, matching f2fs_init_compress_inode(). With compress_cache disabled, ino == max_nid now follows the normal inode path and is rejected as an out-of-range nid.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's f2fs filesystem relates to the handling of the compressed cache inode number (F2FS_COMPRESS_INO()). This inode number uses max_nid as a synthetic inode number, which only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. However, due to is_meta_ino() treating F2FS_COMPRESS_INO() as a meta inode unconditionally, the inode range check in do_read_inode() was bypassed, allowing f2fs_iget() to instantiate a fake internal inode. The patch corrects this by gating the compressed cache inode case on the compress_cache option, so that with compression disabled, out-of-range inode numbers are rejected normally.
Potential Impact
This vulnerability could allow a corrupted directory entry with an out-of-range inode number to bypass inode validation checks, potentially leading to the instantiation of a fake internal inode within the kernel's f2fs filesystem. This could cause undefined behavior or memory corruption within the kernel, impacting system stability or security. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly gate the compressed cache inode validation on the compress_cache mount option. Users should update their Linux kernel to a version that includes this fix once available. Patch status is not yet confirmed from the vendor advisory; check the official Linux kernel release notes or vendor advisories for the specific fixed version and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-cv79-fx5q-34h3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63817"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ad2a4a8d5989131bf4
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/19/2026, 20:21:14 UTC
Last updated: 08/31/2026, 22:52:13 UTC
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.