Answer in brief
CVE-2026-63818 records a Unknown severity vulnerability in f2fs: validate orphan inode entry count. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63818 records a Unknown severity vulnerability in f2fs: validate orphan inode entry count. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <210c210c92d78fdf5051bc55c5c69044b1a2150a || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <ad101d15716f5a24d1fa82a849f80430c805a3dd || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <d2f236196d542ccd8505736e41c3a1d3f0305f6f || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <550511a2470f6d204fa07b331f048bd2d3c51280 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <8aad54746c251f2c2370118df766c0c82e2d2091 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <2e12381d4495dc8b0ff042c6856022b2e359835c || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <846c499a65816d13f1186e3090e825e8bb8bcb8b | 210c210c92d78fdf5051bc55c5c69044b1a2150a, ad101d15716f5a24d1fa82a849f80430c805a3dd, d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70, d2f236196d542ccd8505736e41c3a1d3f0305f6f, 550511a2470f6d204fa07b331f048bd2d3c51280, 8aad54746c251f2c2370118df766c0c82e2d2091, 2e12381d4495dc8b0ff042c6856022b2e359835c, 846c499a65816d13f1186e3090e825e8bb8bcb8b |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <210c210c92d78fdf5051bc55c5c69044b1a2150a || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <ad101d15716f5a24d1fa82a849f80430c805a3dd || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <d2f236196d542ccd8505736e41c3a1d3f0305f6f || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <550511a2470f6d204fa07b331f048bd2d3c51280 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <8aad54746c251f2c2370118df766c0c82e2d2091 || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <2e12381d4495dc8b0ff042c6856022b2e359835c || >=127e670abfa7fa150f6550d620ded930f5bdb4e7 <846c499a65816d13f1186e3090e825e8bb8bcb8b | 210c210c92d78fdf5051bc55c5c69044b1a2150a, ad101d15716f5a24d1fa82a849f80430c805a3dd, d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70, d2f236196d542ccd8505736e41c3a1d3f0305f6f, 550511a2470f6d204fa07b331f048bd2d3c51280, 8aad54746c251f2c2370118df766c0c82e2d2091, 2e12381d4495dc8b0ff042c6856022b2e359835c, 846c499a65816d13f1186e3090e825e8bb8bcb8b |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.