CVE-2026-63819

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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

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: 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(high)
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
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 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.

Data Freshness Timeline

(refreshed 22× in last 7d / 48× 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 10:58 UTCGHSA enrichment
  3. 2026-07-26 23:03 UTCGHSA enrichment
  4. 2026-07-26 11:09 UTCEG score recompute
  5. 2026-07-26 11:08 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:22 UTCEG score recompute
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:25 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-20 17:44 UTCEG score recompute
  18. 2026-07-20 17:44 UTCGHSA enrichment
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-20 14:44 UTCEG score recompute▲ 7.80
  21. 2026-07-20 14:43 UTCGHSA enrichment
  22. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-07-20 08:34 UTCNVD update
  24. 2026-07-20 07:07 UTCMITRE cvelistV5
  25. 2026-07-19 15:26 UTCGHSA enrichment
Show 23 more
  1. 2026-07-19 15:18 UTCGHSA enrichment
  2. 2026-07-19 15:16 UTCGHSA enrichment
  3. 2026-07-19 15:15 UTCGHSA enrichment
  4. 2026-07-19 15:15 UTCGHSA enrichment
  5. 2026-07-19 15:14 UTCGHSA enrichment
  6. 2026-07-19 15:13 UTCGHSA enrichment
  7. 2026-07-19 15:12 UTCGHSA enrichment
  8. 2026-07-19 15:09 UTCGHSA enrichment
  9. 2026-07-19 14:52 UTCGHSA enrichment
  10. 2026-07-19 14:25 UTCGHSA enrichment
  11. 2026-07-19 14:16 UTCGHSA enrichment
  12. 2026-07-19 14:13 UTCGHSA enrichment
  13. 2026-07-19 14:08 UTCGHSA enrichment
  14. 2026-07-19 13:59 UTCGHSA enrichment
  15. 2026-07-19 13:53 UTCGHSA enrichment
  16. 2026-07-19 13:50 UTCGHSA enrichment
  17. 2026-07-19 13:46 UTCGHSA enrichment
  18. 2026-07-19 13:13 UTCGHSA enrichment
  19. 2026-07-19 13:06 UTCGHSA enrichment
  20. 2026-07-19 13:00 UTCGHSA enrichment
  21. 2026-07-19 12:26 UTCNVD update
  22. 2026-07-19 12:13 UTCEG score recompute
  23. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

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 July 20, 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 98.0% 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs