CVE-2026-63818

f2fs: validate orphan inode entry count

HIGH
8.4
CVSS Score
Published: July 19, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.4
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8 ≤ v < 5.10.2613.8 ≤ v < 5.15.2123.8 ≤ v < 6.1.1783.8 ≤ v < 6.12.963.8 ≤ v < 6.18.383.8 ≤ v < 6.6.1453.8 ≤ v < 7.1.33.8 ≤ v < 7.2127e670abfa7fa150f6550d620ded930f5bdb4e73.8
Vendor states this is fixed in 210c210c92d78fdf5051bc55c5c69044b1a2150a (fixed)
Vendor states this is fixed in 2e12381d4495dc8b0ff042c6856022b2e359835c (fixed)
Vendor states this is fixed in 550511a2470f6d204fa07b331f048bd2d3c51280 (fixed)
Vendor states this is fixed in 846c499a65816d13f1186e3090e825e8bb8bcb8b (fixed)
Vendor states this is fixed in 8aad54746c251f2c2370118df766c0c82e2d2091 (fixed)
Vendor states this is fixed in ad101d15716f5a24d1fa82a849f80430c805a3dd (fixed)
Vendor states this is fixed in d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70 (fixed)
Vendor states this is fixed in d2f236196d542ccd8505736e41c3a1d3f0305f6f (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

8.4HIGHLinux
Vector?

Quick Info

StatusAWAITING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card