CVE-2026-63818 json
f2fs: validate orphan inode entry count
published 3mo ago modified yesterday also EUVD-2026-45484
- cvss
- 8.4
- 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 3%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: validate orphan inode entry count
f2fs_recover_orphan_inodes() trusts the orphan block entry_count when replaying orphan inodes from the checkpoint pack. A corrupted entry_count larger than F2FS_ORPHANS_PER_BLOCK makes the recovery loop read past the ino[] array and interpret footer or following data as inode numbers.
On a crafted image, mounting an unpatched kernel can drive orphan recovery into f2fs_bug_on() and panic the kernel. Validate entry_count before consuming entries so corrupted checkpoint data fails the mount with -EFSCORRUPTED and requests fsck instead.
Set ERROR_INCONSISTENT_ORPHAN as well, so the corruption reason can be recorded in the superblock s_errors[] field. This gives fsck a persistent hint even though mount-time orphan recovery failure may leave no chance to persist SBI_NEED_FSCK through a checkpoint.
Patch / fix
- Linux Linux 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.38, 7.1.3, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.96-1
- linux Debian 14 7.1.3-1
- linux-6.12 Debian 12 6.12.100-1~deb12u1
debian advisories DEBIAN-CVE-2026-63818
- 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-63818
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/210c210c92d78fdf5051bc55c5c69044b1a2150a commit
- git.kernel.org/stable/c/ad101d15716f5a24d1fa82a849f80430c805a3dd commit
- git.kernel.org/stable/c/d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70 commit
- git.kernel.org/stable/c/d2f236196d542ccd8505736e41c3a1d3f0305f6f commit
- git.kernel.org/stable/c/550511a2470f6d204fa07b331f048bd2d3c51280 commit
- git.kernel.org/stable/c/8aad54746c251f2c2370118df766c0c82e2d2091 commit
- git.kernel.org/stable/c/2e12381d4495dc8b0ff042c6856022b2e359835c commit
- git.kernel.org/stable/c/846c499a65816d13f1186e3090e825e8bb8bcb8b commit
Is CVE-2026-63818 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-63818 updated
kernel: f2fs: validate orphan inode entry count
-
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.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/210c210c92d78fdf5051bc55c5c69044b1a2150a
patch
-
git.kernel.org
/stable/c/ad101d15716f5a24d1fa82a849f80430c805a3dd
patch
-
git.kernel.org
/stable/c/d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70
patch
-
git.kernel.org
/stable/c/d2f236196d542ccd8505736e41c3a1d3f0305f6f
patch
-
git.kernel.org
/stable/c/550511a2470f6d204fa07b331f048bd2d3c51280
patch
-
git.kernel.org
/stable/c/8aad54746c251f2c2370118df766c0c82e2d2091
patch
-
git.kernel.org
/stable/c/2e12381d4495dc8b0ff042c6856022b2e359835c
patch
-
git.kernel.org
/stable/c/846c499a65816d13f1186e3090e825e8bb8bcb8b
patch
Sources
- CVE List CVE-2026-63818
- NVD CVE-2026-63818
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.