CVE-2026-63818

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM 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

A fix is available — apply it.

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(medium)
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
4%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 84× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-11 20:32 UTCEG score recompute
  2. 2026-09-11 20:32 UTCVendor advisory
  3. 2026-09-11 20:32 UTCGHSA enrichment
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 23:44 UTCEG score recompute
  7. 2026-09-07 23:44 UTCVendor advisory
  8. 2026-09-07 23:44 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:15 UTCGHSA enrichment
  12. 2026-09-05 20:14 UTCEG score recompute
  13. 2026-09-05 20:14 UTCGHSA enrichment
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 03:43 UTCEG score recompute
  19. 2026-08-31 03:43 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 15:43 UTCGHSA enrichment
  22. 2026-08-30 03:03 UTCEG score recompute
  23. 2026-08-30 03:03 UTCGHSA enrichment
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-28 01:44 UTCEG score recompute
  2. 2026-08-28 01:44 UTCGHSA enrichment
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-27 12:51 UTCGHSA enrichment
  5. 2026-08-27 00:52 UTCEG score recompute
  6. 2026-08-27 00:52 UTCGHSA enrichment
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 12:52 UTCGHSA enrichment
  9. 2026-08-26 00:53 UTCEG score recompute
  10. 2026-08-26 00:53 UTCGHSA enrichment
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 12:16 UTCGHSA enrichment
  13. 2026-08-25 00:15 UTCEG score recompute
  14. 2026-08-25 00:15 UTCGHSA enrichment
  15. 2026-08-24 12:15 UTCEG score recompute
  16. 2026-08-24 12:15 UTCGHSA enrichment
  17. 2026-08-24 00:15 UTCGHSA enrichment
  18. 2026-08-23 12:15 UTCEG score recompute
  19. 2026-08-23 12:15 UTCGHSA enrichment
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-23 00:16 UTCGHSA enrichment
  22. 2026-08-22 12:11 UTCEG score recompute
  23. 2026-08-22 12:11 UTCGHSA enrichment
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 23:43 UTCGHSA enrichment
  26. 2026-08-21 11:44 UTCGHSA enrichment
  27. 2026-08-20 23:13 UTCEG score recompute
  28. 2026-08-20 23:13 UTCGHSA enrichment
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 11:14 UTCGHSA enrichment
  31. 2026-08-19 23:15 UTCEG score recompute
  32. 2026-08-19 23:15 UTCGHSA enrichment
  33. 2026-08-19 17:04 UTCEPSS rescore
  34. 2026-08-19 07:55 UTCGHSA enrichment
  35. 2026-08-18 19:51 UTCEG score recompute
  36. 2026-08-18 19:51 UTCGHSA enrichment
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-18 05:54 UTCGHSA enrichment
  39. 2026-08-17 17:35 UTCEG score recompute
  40. 2026-08-17 17:35 UTCGHSA enrichment
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-17 05:23 UTCGHSA enrichment
  43. 2026-08-17 01:21 UTCEG score recompute
  44. 2026-08-17 01:21 UTCGHSA enrichment
  45. 2026-08-16 14:56 UTCEPSS rescore
  46. 2026-08-16 13:22 UTCEG score recompute
  47. 2026-08-16 13:22 UTCGHSA enrichment
  48. 2026-08-16 01:23 UTCGHSA enrichment
  49. 2026-08-15 13:24 UTCEG score recompute
  50. 2026-08-15 13:24 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-15 01:24 UTCGHSA enrichment
  53. 2026-08-14 13:26 UTCGHSA enrichment
  54. 2026-08-14 01:26 UTCEG score recompute
  55. 2026-08-14 01:26 UTCGHSA enrichment
  56. 2026-08-13 22:00 UTCEPSS rescore
  57. 2026-08-13 13:27 UTCGHSA enrichment
  58. 2026-08-13 01:28 UTCEG score recompute
  59. 2026-08-13 01:28 UTCGHSA enrichment
  60. 2026-08-12 13:51 UTCEPSS rescore
  61. 2026-08-12 13:29 UTCGHSA enrichment
  62. 2026-08-12 01:27 UTCEG score recompute
  63. 2026-08-12 01:27 UTCGHSA enrichment
  64. 2026-08-11 13:28 UTCGHSA enrichment
  65. 2026-08-11 01:29 UTCEG score recompute
  66. 2026-08-11 01:29 UTCGHSA enrichment
  67. 2026-08-11 00:00 UTCEPSS rescore
  68. 2026-08-10 13:30 UTCGHSA enrichment
  69. 2026-08-10 01:23 UTCEG score recompute
  70. 2026-08-10 01:23 UTCGHSA enrichment
  71. 2026-08-09 13:47 UTCEPSS rescore
  72. 2026-08-09 13:24 UTCGHSA enrichment
  73. 2026-08-09 01:25 UTCEG score recompute
  74. 2026-08-09 01:25 UTCGHSA enrichment
  75. 2026-08-08 16:37 UTCEPSS rescore

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 August 17, 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.3% 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

See which npm, PyPI, Go, and Maven packages are affected by 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