CVE-2026-63817 json
f2fs: validate compress cache inode only when enabled
published 3mo ago modified yesterday also EUVD-2026-45483
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.14, 5.15.212, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2
- linux Debian 12 6.1.177-1
- linux Debian 13 6.12.95-1
- linux Debian 14 7.1.3-1
debian advisories DEBIAN-CVE-2026-63817
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-63817
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.1.4-1.1
opensuse advisories openSUSE-SU-2026:11339-1
- git.kernel.org/stable/c/fcc051d377a9701a452e7663a1a8223c26225df9 commit
- git.kernel.org/stable/c/29115b8c9172d34e67ab26cc4f6c209b7a236d7a commit
- git.kernel.org/stable/c/13e4b59d3a9413f66f116fa6c4828519b960a5ea commit
- git.kernel.org/stable/c/16161444c30d8dff9428abbae42b72ce4e32a932 commit
- git.kernel.org/stable/c/77f216ff9ce5cde8eed9f6d12707e906dffdc9f7 commit
- git.kernel.org/stable/c/0969926d987bbde9a1aa49da317582ba37095805 commit
- git.kernel.org/stable/c/5073c66a96a9c23c0c2533ed4ed06e42f9021208 commit
Is CVE-2026-63817 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-63817 updated
kernel: f2fs: validate compress cache inode only when enabled
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/fcc051d377a9701a452e7663a1a8223c26225df9
patch
-
git.kernel.org
/stable/c/29115b8c9172d34e67ab26cc4f6c209b7a236d7a
patch
-
git.kernel.org
/stable/c/13e4b59d3a9413f66f116fa6c4828519b960a5ea
patch
-
git.kernel.org
/stable/c/16161444c30d8dff9428abbae42b72ce4e32a932
patch
-
git.kernel.org
/stable/c/77f216ff9ce5cde8eed9f6d12707e906dffdc9f7
patch
-
git.kernel.org
/stable/c/0969926d987bbde9a1aa49da317582ba37095805
patch
-
git.kernel.org
/stable/c/5073c66a96a9c23c0c2533ed4ed06e42f9021208
patch
Sources
- CVE List CVE-2026-63817
- NVD CVE-2026-63817
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.