Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63818f2fs: validate orphan inode entry count

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 29 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63818, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.

Affected products

  • Linux · Linux

    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < 210c210c92d78fdf5051bc55c5c69044b1a2150a
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < ad101d15716f5a24d1fa82a849f80430c805a3dd
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < d2f236196d542ccd8505736e41c3a1d3f0305f6f
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < 550511a2470f6d204fa07b331f048bd2d3c51280
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < 8aad54746c251f2c2370118df766c0c82e2d2091
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < 2e12381d4495dc8b0ff042c6856022b2e359835c
    • affected 127e670abfa7fa150f6550d620ded930f5bdb4e7 – < 846c499a65816d13f1186e3090e825e8bb8bcb8b
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63818 badge
[![CVE-2026-63818](https://cveledger.app/badge/CVE-2026-63818.svg)](https://cveledger.app/cve/CVE-2026-63818)

Record last updated .