CVE-2026-31450

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ext4: publish jinode after initialization

ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset.

The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash.

Below is the crash I observe: 

BUG: unable to handle page fault for address: 000000010beb47f4
PGD 110e51067 P4D 110e51067 PUD 0
Oops: Oops: 0000 [#1] SMP NOPTI
CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014
RIP: 0010:xas_find_marked+0x3d/0x2e0
Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02
RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246
RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003
RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10
RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec
R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000
R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88
FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0
PKRU: 55555554
Call Trace:
filemap_get_folios_tag+0x87/0x2a0
__filemap_fdatawait_range+0x5f/0xd0
? srso_alias_return_thunk+0x5/0xfbef5
? __schedule+0x3e7/0x10c0
? srso_alias_return_thunk+0x5/0xfbef5
? srso_alias_return_thunk+0x5/0xfbef5
? srso_alias_return_thunk+0x5/0xfbef5
? preempt_count_sub+0x5f/0x80
? srso_alias_return_thunk+0x5/0xfbef5
? cap_safe_nice+0x37/0x70
? srso_alias_return_thunk+0x5/0xfbef5
? preempt_count_sub+0x5f/0x80
? srso_alias_return_thunk+0x5/0xfbef5
filemap_fdatawait_range_keep_errors+0x12/0x40
ext4_fc_commit+0x697/0x8b0
? ext4_file_write_iter+0x64b/0x950
? srso_alias_return_thunk+0x5/0xfbef5
? preempt_count_sub+0x5f/0x80
? srso_alias_return_thunk+0x5/0xfbef5
? vfs_write+0x356/0x480
? srso_alias_return_thunk+0x5/0xfbef5
? preempt_count_sub+0x5f/0x80
ext4_sync_file+0xf7/0x370
do_fsync+0x3b/0x80
? syscall_trace_enter+0x108/0x1d0
__x64_sys_fdatasync+0x16/0x20
do_syscall_64+0x62/0x2c0
entry_SYSCALL_64_after_hwframe+0x76/0x7e
...

Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 22, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated May 2, 2026
Patch available.
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e76bcb727e4874a2f9d0297f8e3f8eced89b0764
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4325e84727e539c8597bd5b8491349f57f7fb17
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be54c0055407a73b60349c093c8ce621cb8fa232
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a070d5a872ffe0e0fe5c46eda6386140ded39adb
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4855a59e21789c79f003a9b5f4135c95a7495c6b
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33f486987af21531a7b18973d11795ede3da9ddd
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d2b648960147d078b000b9a7494017082024366
Web page

ext4: publish jinode after initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1aec30021edd410b986c156f195f3d23959a9d11

Vendor Advisories for CVE-2026-31450(2)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-19ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-19ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1061.62~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-19ubuntu
linuxKernel @ 5.10.253 (fixes >=3.11.0)—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)
  • every version up to 6.19.11-1: fixed in 6.19.11-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 301 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 206 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 19:34 UTCEG score recompute
  2. 2026-10-19 19:34 UTCVendor advisory
  3. 2026-10-19 19:34 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-10-19 18:49 UTCEG score recompute
  5. 2026-10-19 18:49 UTCVendor advisory
  6. 2026-10-19 18:48 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-18 03:48 UTCEG score recompute
  10. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-16 15:21 UTCEG score recompute
  13. 2026-10-16 15:21 UTCVendor advisory
  14. 2026-10-16 15:21 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-10-15 02:35 UTCEG score recompute
  17. 2026-10-15 02:35 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-15 01:39 UTCEG score recompute
  19. 2026-10-15 01:39 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-10-12 16:15 UTCEG score recompute
  24. 2026-10-11 19:57 UTCEG score recompute
  25. 2026-10-11 17:11 UTCEG score recompute
Show 70 more
  1. 2026-10-11 14:39 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  6. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  12. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  13. 2026-09-28 00:49 UTCOSV refresh
  14. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  16. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-09-08 09:10 UTCEG score recompute
  27. 2026-09-08 09:10 UTCVendor advisory
  28. 2026-09-08 09:09 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-09-02 03:04 UTCOSV refresh
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  42. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-08-16 06:01 UTCEG score recompute
  51. 2026-08-16 06:01 UTCVendor advisory
  52. 2026-08-16 06:01 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  53. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  54. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  55. 2026-08-14 17:06 UTCVendor advisory
  56. 2026-08-14 17:06 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  57. 2026-08-14 04:20 UTCEG score recompute
  58. 2026-08-14 04:20 UTCVendor advisory
  59. 2026-08-14 04:20 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  61. 2026-08-13 08:40 UTCVendor advisory
  62. 2026-08-13 08:39 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-08-12 18:32 UTCEG score recompute
  64. 2026-08-12 18:32 UTCVendor advisory
  65. 2026-08-12 18:32 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-08-11 16:47 UTCEG score recompute
  68. 2026-08-11 16:47 UTCVendor advisory
  69. 2026-08-11 16:47 UTCGHSA enrichmentGHSA-fr68-gvh3-4qhv · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-08-11 02:22 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31450?
CVE-2026-31450 is a high-severity vulnerability; its CVE record was published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4inodeattach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2journalinitjbdinode(), allowing a reader to observe a non-NULL jinode with ivfsinode…
When was the CVE record for CVE-2026-31450 published?
The CVE record for CVE-2026-31450 was published on April 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-31450 actively exploited?
CVE-2026-31450 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31450?
CVE-2026-31450 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-31450?
A fix for CVE-2026-31450 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31450 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31450

Explore →

Is Your Infrastructure Affected by CVE-2026-31450?

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

Book a Demo →Browse All CVEs