CVE-2025-68337

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-12-22. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 6 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted

There's issue when file system corrupted: ------------[ cut here ]------------ kernel BUG at fs/jbd2/transaction.c:1289! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next RIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0 RSP: 0018:ffff888117aafa30 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534 RDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010 RBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028 R10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0 Call Trace: __ext4_journal_get_create_access+0x42/0x170 ext4_getblk+0x319/0x6f0 ext4_bread+0x11/0x100 ext4_append+0x1e6/0x4a0 ext4_init_new_dir+0x145/0x1d0 ext4_mkdir+0x326/0x920 vfs_mkdir+0x45c/0x740 do_mkdirat+0x234/0x2f0 __x64_sys_mkdir+0xd6/0x120 do_syscall_64+0x5f/0xfa0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The above issue occurs with us in errors=continue mode when accompanied by storage failures. There have been many inconsistencies in the file system data. In the case of file system data inconsistency, for example, if the block bitmap of a referenced block is not set, it can lead to the situation where a block being committed is allocated and used again. As a result, the following condition will not be satisfied then trigger BUG_ON. Of course, it is entirely possible to construct a problematic image that can trigger this BUG_ON through specific operations. In fact, I have constructed such an image and easily reproduced this issue. Therefore, J_ASSERT() holds true only under ideal conditions, but it may not necessarily be satisfied in exceptional scenarios. Using J_ASSERT() directly in abnormal situations would cause the system to crash, which is clearly not what we want. So here we directly trigger a JBD abort instead of immediately invoking BUG_ON.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

December 22, 2025

Last Modified

July 30, 2026

Advisory Details (9)

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

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed62fd8c15d41c4127ad16b8219b63124f5962bc
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf34c72337e40c4670cceeb79b353356933a254b
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b4f8eabf6d991bd41fabcdf9302c4b3eab590cf4
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aa1703f3f706ea0867fb1991dcac709c9ec94cfb
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a2a7f854d154a3e9232fec80782dad951655f52f
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/986835bf4d11032bba4ab8414d18fce038c61bb4
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71bbe06c40fc59b5b15661eca8ff307f4176d7f9
generic

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3faac6531d4818cd6be45e5bbf32937bbbc795c0

Vendor Advisories for CVE-2025-68337(1)

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-05-21ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-05-21ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.173.183~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-6.8.1-1047-realtime (6.8.1-1047.48~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-05-21ubuntu
linuxKernel @ 5.10.248—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.

All Vendor Advisories

(25)

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 16× in last 7d / 51× 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 137 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-68337?
CVE-2025-68337 is a high vulnerability published on December 22, 2025. In the Linux kernel, the following vulnerability has been resolved: jbd2: avoid bugon in jbd2journalgetcreate_access() when file system corrupted There's issue when file system corrupted: ------------[ cut here ]------------ kernel BUG at fs/jbd2/transaction.c:1289! Oops: invalid opcode: 0000 [#1]…
When was CVE-2025-68337 disclosed?
CVE-2025-68337 was first published in the National Vulnerability Database on December 22, 2025, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68337 actively exploited?
CVE-2025-68337 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 62.0% of all scored CVEs.
What is the CVSS score of CVE-2025-68337?
CVE-2025-68337 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-68337?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68337, 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-2025-68337

Explore →

Is Your Infrastructure Affected by CVE-2025-68337?

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

Start Free Scan →Browse All CVEs