CVE-2026-63817

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

f2fs: validate compress cache inode only when enabled

F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is enabled.

When compress_cache is disabled, max_nid is outside the valid inode range. A corrupted directory entry that points to ino == max_nid should therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino() currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally, so f2fs_iget() bypasses do_read_inode() and its nid range check, and instantiates a fake internal inode instead.

Gate the compressed cache inode case on COMPRESS_CACHE, matching f2fs_init_compress_inode(). With compress_cache disabled, ino == max_nid now follows the normal inode path and is rejected as an out-of-range nid.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 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

August 17, 2026

Advisory Details (6)

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

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77f216ff9ce5cde8eed9f6d12707e906dffdc9f7
generic

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5073c66a96a9c23c0c2533ed4ed06e42f9021208
generic

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29115b8c9172d34e67ab26cc4f6c209b7a236d7a
generic

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16161444c30d8dff9428abbae42b72ce4e32a932
generic

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13e4b59d3a9413f66f116fa6c4828519b960a5ea
generic

f2fs: validate compress cache inode only when enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0969926d987bbde9a1aa49da317582ba37095805

Vendor Advisories for CVE-2026-63817(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-24.04-edge (7.0.0-31.31~24.04.1) @ noble2026-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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-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 / 81× 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 173 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 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 23:44 UTCEG score recompute
  8. 2026-09-07 23:44 UTCVendor advisory
  9. 2026-09-07 23:44 UTCGHSA enrichment
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:15 UTCGHSA enrichment
  13. 2026-09-05 20:14 UTCEG score recompute
  14. 2026-09-05 20:14 UTCGHSA enrichment
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 04:40 UTCEG score recompute
  19. 2026-08-31 04:40 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 15:51 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 04:13 UTCGHSA enrichment
  2. 2026-08-27 15:16 UTCEG score recompute
  3. 2026-08-27 15:16 UTCGHSA enrichment
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-27 01:32 UTCEG score recompute
  6. 2026-08-27 01:32 UTCGHSA enrichment
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 12:44 UTCGHSA enrichment
  9. 2026-08-25 23:47 UTCEG score recompute
  10. 2026-08-25 23:46 UTCGHSA enrichment
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 10:47 UTCGHSA enrichment
  13. 2026-08-24 21:56 UTCEG score recompute
  14. 2026-08-24 21:56 UTCGHSA enrichment
  15. 2026-08-24 09:08 UTCGHSA enrichment
  16. 2026-08-23 19:52 UTCGHSA enrichment
  17. 2026-08-23 07:04 UTCEG score recompute
  18. 2026-08-23 07:04 UTCGHSA enrichment
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-22 18:14 UTCGHSA enrichment
  21. 2026-08-22 05:25 UTCEG score recompute
  22. 2026-08-22 05:25 UTCGHSA enrichment
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 16:36 UTCGHSA enrichment
  25. 2026-08-21 03:28 UTCEG score recompute
  26. 2026-08-21 03:28 UTCGHSA enrichment
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-20 14:36 UTCGHSA enrichment
  29. 2026-08-20 00:40 UTCEG score recompute
  30. 2026-08-20 00:40 UTCGHSA enrichment
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-19 11:50 UTCGHSA enrichment
  33. 2026-08-18 22:50 UTCEG score recompute
  34. 2026-08-18 22:50 UTCGHSA enrichment
  35. 2026-08-18 13:48 UTCEPSS rescore
  36. 2026-08-18 09:59 UTCGHSA enrichment
  37. 2026-08-17 21:11 UTCEG score recompute
  38. 2026-08-17 21:11 UTCGHSA enrichment
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-17 05:23 UTCGHSA enrichment
  41. 2026-08-16 18:33 UTCEG score recompute
  42. 2026-08-16 18:33 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 05:44 UTCEG score recompute
  45. 2026-08-16 05:44 UTCGHSA enrichment
  46. 2026-08-15 16:56 UTCGHSA enrichment
  47. 2026-08-15 04:07 UTCEG score recompute
  48. 2026-08-15 04:07 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 15:18 UTCGHSA enrichment
  51. 2026-08-14 02:29 UTCEG score recompute
  52. 2026-08-14 02:29 UTCGHSA enrichment
  53. 2026-08-13 22:00 UTCEPSS rescore
  54. 2026-08-13 13:41 UTCGHSA enrichment
  55. 2026-08-13 00:46 UTCEG score recompute
  56. 2026-08-13 00:46 UTCGHSA enrichment
  57. 2026-08-12 13:51 UTCEPSS rescore
  58. 2026-08-12 11:58 UTCGHSA enrichment
  59. 2026-08-11 23:09 UTCGHSA enrichment
  60. 2026-08-11 10:21 UTCEG score recompute
  61. 2026-08-11 10:21 UTCGHSA enrichment
  62. 2026-08-11 00:00 UTCEPSS rescore
  63. 2026-08-10 21:33 UTCGHSA enrichment
  64. 2026-08-10 08:44 UTCGHSA enrichment
  65. 2026-08-09 19:56 UTCEG score recompute
  66. 2026-08-09 19:56 UTCGHSA enrichment
  67. 2026-08-09 13:47 UTCEPSS rescore
  68. 2026-08-09 07:08 UTCGHSA enrichment
  69. 2026-08-08 18:20 UTCEG score recompute
  70. 2026-08-08 18:20 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 05:31 UTCGHSA enrichment
  73. 2026-08-07 16:43 UTCEG score recompute
  74. 2026-08-07 16:43 UTCGHSA enrichment
  75. 2026-08-07 03:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-63817?
CVE-2026-63817 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: validate compress cache inode only when enabled F2FSCOMPRESSINO() uses NMI(sbi)->maxnid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is…
When was CVE-2026-63817 disclosed?
CVE-2026-63817 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-63817 actively exploited?
CVE-2026-63817 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-63817?
CVE-2026-63817 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-63817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63817, 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-63817

Explore →

Is Your Infrastructure Affected by CVE-2026-63817?

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

Start Free Scan →Browse All CVEs