Menu

Star on GitHub · 3.2k

CVE-2026-63817

7.8 · HIGH

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…

Published Jul 19, 2026EPSS 0.13%

Overview

CVE-2026-63817 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-63817?

CVE-2026-63817 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-63817?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-63817?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-63817?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-63817 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all