CVE-2026-63819

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: fix to do sanity check on f2fs_get_node_folio_ra()

kernel BUG at fs/f2fs/file.c:845! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5336 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:f2fs_do_truncate_blocks+0x1115/0x1140 fs/f2fs/file.c:845 Code: fc fc 90 0f 0b e8 8b 9d 9a fd 90 0f 0b e8 83 9d 9a fd 48 89 df 48 c7 c6 60 d1 1a 8c e8 54 f1 fc fc 90 0f 0b e8 6c 9d 9a fd 90 <0f> 0b e8 64 9d 9a fd 90 0f 0b 90 e9 93 fd ff ff e8 56 9d 9a fd 90 RSP: 0018:ffffc9000e4474c0 EFLAGS: 00010283 RAX: ffffffff842b1d34 RBX: 0000000000000003 RCX: 0000000000100000 RDX: ffffc9000f03a000 RSI: 0000000000035503 RDI: 0000000000035504 RBP: ffffc9000e447608 R08: ffff8880123b0000 R09: 0000000000000002 R10: 00000000fffffffe R11: 0000000000000002 R12: 0000000000000001 R13: 0000000000000000 R14: 1ffff92001c88ea0 R15: 00000000ffff039c FS: 00007f7e02ee36c0(0000) GS:ffff88808c887000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff0305c4000 CR3: 0000000012d4c000 CR4: 0000000000352ef0 Call Trace: f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:882 f2fs_truncate+0x471/0x7c0 fs/f2fs/file.c:940 f2fs_evict_inode+0xa3f/0x1ac0 fs/f2fs/inode.c:907 evict+0x61e/0xb10 fs/inode.c:841 f2fs_fill_super+0x5f43/0x78f0 fs/f2fs/super.c:5224 get_tree_bdev_flags+0x431/0x4f0 fs/super.c:1694 vfs_get_tree+0x92/0x2a0 fs/super.c:1754 fc_mount fs/namespace.c:1193 [inline] do_new_mount_fc fs/namespace.c:3758 [inline] do_new_mount+0x341/0xd30 fs/namespace.c:3834 do_mount fs/namespace.c:4167 [inline] __do_sys_mount fs/namespace.c:4383 [inline] __se_sys_mount+0x31d/0x420 fs/namespace.c:4360 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

count = ADDRS_PER_PAGE(dn.node_folio, inode);

count -= dn.ofs_in_node; f2fs_bug_on(sbi, count < 0);

The fuzz test will trigger above bug_on in f2fs.

The root cause should be: in the corrupted inode, there is a direct node which has the same ino and nid in its footer, so in f2fs_do_truncate_blocks(), after f2fs_get_dnode_of_data() finds such dnode: 1) ADDRS_PER_PAGE(dn.node_folio, inode) will return 923 2) once dn.ofs_in_node points to addr[923, 1017] Then it will trigger the system panic.

Let's introduce NODE_TYPE_NON_IXNODE to indicate current node should not be an inode or xattr node, and then use it in below path to detect inconsistent node chain in inode mapping table:

  • f2fs_do_truncate_blocks
  • f2fs_get_dnode_of_data
  • f2fs_get_node_folio_ra
  • __get_node_folio
  • f2fs_sanity_check_node_footer
  • case NODE_TYPE_NON_IXNODE -> check whether it is inode|xnode

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
7%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

f2fs: fix to do sanity check on f2fs_get_node_folio_ra() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8712353ed80f87271d732297567dcdbe4b84e8c7
generic

f2fs: fix to do sanity check on f2fs_get_node_folio_ra() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/406c28af75123432d38cf9bbaa6f1476f7b14770
generic

f2fs: fix to do sanity check on f2fs_get_node_folio_ra() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cc21c1ffe15b4156b0bf744f32fd1faef0b7c73

Vendor Advisories for CVE-2026-63819(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-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-07ubuntu

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
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
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 12× in last 7d / 79× 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 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 23:44 UTCEG score recompute
  5. 2026-09-07 23:44 UTCVendor advisory
  6. 2026-09-07 23:44 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 13:15 UTCGHSA enrichment
  10. 2026-09-05 20:14 UTCEG score recompute
  11. 2026-09-05 20:14 UTCGHSA enrichment
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-31 03:38 UTCEG score recompute
  17. 2026-08-31 03:38 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 15:43 UTCGHSA enrichment
  20. 2026-08-30 03:03 UTCEG score recompute
  21. 2026-08-30 03:03 UTCGHSA enrichment
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-27 23:52 UTCEG score recompute
  25. 2026-08-27 23:52 UTCGHSA enrichment
Show 75 more
  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-27 11:58 UTCGHSA enrichment
  3. 2026-08-26 23:40 UTCEG score recompute
  4. 2026-08-26 23:40 UTCGHSA enrichment
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-26 11:46 UTCGHSA enrichment
  7. 2026-08-25 23:47 UTCEG score recompute
  8. 2026-08-25 23:46 UTCGHSA enrichment
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 10:56 UTCGHSA enrichment
  11. 2026-08-24 23:02 UTCEG score recompute
  12. 2026-08-24 23:02 UTCGHSA enrichment
  13. 2026-08-24 11:08 UTCEG score recompute
  14. 2026-08-24 11:08 UTCGHSA enrichment
  15. 2026-08-23 23:14 UTCGHSA enrichment
  16. 2026-08-23 11:20 UTCEG score recompute
  17. 2026-08-23 11:20 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 23:26 UTCGHSA enrichment
  20. 2026-08-22 11:32 UTCGHSA enrichment
  21. 2026-08-21 23:38 UTCGHSA enrichment
  22. 2026-08-21 11:44 UTCGHSA enrichment
  23. 2026-08-20 23:02 UTCEG score recompute
  24. 2026-08-20 23:02 UTCGHSA enrichment
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 11:07 UTCGHSA enrichment
  27. 2026-08-19 23:14 UTCEG score recompute
  28. 2026-08-19 23:14 UTCGHSA enrichment
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 07:45 UTCGHSA enrichment
  31. 2026-08-18 19:51 UTCEG score recompute
  32. 2026-08-18 19:51 UTCGHSA enrichment
  33. 2026-08-18 05:54 UTCGHSA enrichment
  34. 2026-08-17 17:17 UTCEG score recompute
  35. 2026-08-17 17:17 UTCGHSA enrichment
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-17 05:23 UTCGHSA enrichment
  38. 2026-08-16 23:10 UTCEG score recompute
  39. 2026-08-16 23:10 UTCGHSA enrichment
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 11:16 UTCEG score recompute
  42. 2026-08-16 11:16 UTCGHSA enrichment
  43. 2026-08-15 23:23 UTCGHSA enrichment
  44. 2026-08-15 11:29 UTCEG score recompute
  45. 2026-08-15 11:29 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-14 23:35 UTCGHSA enrichment
  48. 2026-08-14 11:41 UTCGHSA enrichment
  49. 2026-08-13 23:48 UTCEG score recompute
  50. 2026-08-13 23:48 UTCGHSA enrichment
  51. 2026-08-13 22:00 UTCEPSS rescore
  52. 2026-08-13 11:52 UTCGHSA enrichment
  53. 2026-08-12 23:59 UTCEG score recompute
  54. 2026-08-12 23:59 UTCGHSA enrichment
  55. 2026-08-12 13:51 UTCEPSS rescore
  56. 2026-08-12 12:05 UTCGHSA enrichment
  57. 2026-08-12 00:11 UTCEG score recompute
  58. 2026-08-12 00:11 UTCGHSA enrichment
  59. 2026-08-11 12:17 UTCGHSA enrichment
  60. 2026-08-11 00:23 UTCEG score recompute
  61. 2026-08-11 00:23 UTCGHSA enrichment
  62. 2026-08-11 00:00 UTCEPSS rescore
  63. 2026-08-10 12:30 UTCGHSA enrichment
  64. 2026-08-10 00:35 UTCEG score recompute
  65. 2026-08-10 00:35 UTCGHSA enrichment
  66. 2026-08-09 13:47 UTCEPSS rescore
  67. 2026-08-09 12:42 UTCGHSA enrichment
  68. 2026-08-09 00:48 UTCEG score recompute
  69. 2026-08-09 00:48 UTCGHSA enrichment
  70. 2026-08-08 16:37 UTCEPSS rescore
  71. 2026-08-08 12:54 UTCGHSA enrichment
  72. 2026-08-08 01:00 UTCGHSA enrichment
  73. 2026-08-07 13:06 UTCGHSA enrichment
  74. 2026-08-07 01:12 UTCEG score recompute
  75. 2026-08-07 01:12 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-63819?
CVE-2026-63819 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on f2fsgetnodefoliora() kernel BUG at fs/f2fs/file.c:845! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5336 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU…
When was CVE-2026-63819 disclosed?
CVE-2026-63819 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-63819 actively exploited?
CVE-2026-63819 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 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-63819?
CVE-2026-63819 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-63819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63819, 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-63819

Explore →

Is Your Infrastructure Affected by CVE-2026-63819?

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