CVE-2026-63818

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

f2fs: validate orphan inode entry count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8aad54746c251f2c2370118df766c0c82e2d2091
generic

f2fs: validate orphan inode entry count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/846c499a65816d13f1186e3090e825e8bb8bcb8b
generic

f2fs: validate orphan inode entry count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/550511a2470f6d204fa07b331f048bd2d3c51280
generic

f2fs: validate orphan inode entry count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e12381d4495dc8b0ff042c6856022b2e359835c

Vendor Advisories for CVE-2026-63818(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 23× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 04:35 UTCGHSA enrichment
  3. 2026-07-26 16:33 UTCEG score recompute
  4. 2026-07-26 16:33 UTCGHSA enrichment
  5. 2026-07-26 04:31 UTCEG score recompute
  6. 2026-07-26 04:31 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:22 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-20 17:44 UTCEG score recompute
  19. 2026-07-20 17:44 UTCGHSA enrichment
  20. 2026-07-20 17:08 UTCEPSS rescore
  21. 2026-07-20 14:44 UTCEG score recompute▲ 8.40
  22. 2026-07-20 14:43 UTCGHSA enrichment
  23. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  24. 2026-07-19 15:26 UTCGHSA enrichment
  25. 2026-07-19 15:15 UTCGHSA enrichment
Show 12 more
  1. 2026-07-19 15:15 UTCGHSA enrichment
  2. 2026-07-19 15:14 UTCGHSA enrichment
  3. 2026-07-19 15:12 UTCGHSA enrichment
  4. 2026-07-19 15:09 UTCGHSA enrichment
  5. 2026-07-19 14:52 UTCGHSA enrichment
  6. 2026-07-19 14:25 UTCGHSA enrichment
  7. 2026-07-19 14:08 UTCGHSA enrichment
  8. 2026-07-19 13:46 UTCGHSA enrichment
  9. 2026-07-19 13:00 UTCGHSA enrichment
  10. 2026-07-19 12:26 UTCNVD update
  11. 2026-07-19 12:13 UTCEG score recompute
  12. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63818?
CVE-2026-63818 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: validate orphan inode entry count f2fsrecoverorphaninodes() trusts the orphan block entrycount when replaying orphan inodes from the checkpoint pack. A corrupted entry_count larger than F2FSORPHANSPER_BLOCK makes the recovery…
When was CVE-2026-63818 disclosed?
CVE-2026-63818 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63818 actively exploited?
CVE-2026-63818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-63818?
CVE-2026-63818 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-63818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63818, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63818

Explore →

Is Your Infrastructure Affected by CVE-2026-63818?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs