CVE-2023-52604

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-03-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree

Syzkaller reported the following issue:

UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2867:6 index 196694 is out of range for type 's8[1365]' (aka 'signed char[1365]') CPU: 1 PID: 109 Comm: jfsCommit Not tainted 6.6.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 dbAdjTree+0x474/0x4f0 fs/jfs/jfs_dmap.c:2867 dbJoin+0x210/0x2d0 fs/jfs/jfs_dmap.c:2834 dbFreeBits+0x4eb/0xda0 fs/jfs/jfs_dmap.c:2331 dbFreeDmap fs/jfs/jfs_dmap.c:2080 [inline] dbFree+0x343/0x650 fs/jfs/jfs_dmap.c:402 txFreeMap+0x798/0xd50 fs/jfs/jfs_txnmgr.c:2534 txUpdateMap+0x342/0x9e0 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x47a/0xb70 fs/jfs/jfs_txnmgr.c:2732 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 ================================================================================ Kernel panic - not syncing: UBSAN: panic_on_warn set ... CPU: 1 PID: 109 Comm: jfsCommit Not tainted 6.6.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 panic+0x30f/0x770 kernel/panic.c:340 check_panic_on_warn+0x82/0xa0 kernel/panic.c:236 ubsan_epilogue lib/ubsan.c:223 [inline] __ubsan_handle_out_of_bounds+0x13c/0x150 lib/ubsan.c:348 dbAdjTree+0x474/0x4f0 fs/jfs/jfs_dmap.c:2867 dbJoin+0x210/0x2d0 fs/jfs/jfs_dmap.c:2834 dbFreeBits+0x4eb/0xda0 fs/jfs/jfs_dmap.c:2331 dbFreeDmap fs/jfs/jfs_dmap.c:2080 [inline] dbFree+0x343/0x650 fs/jfs/jfs_dmap.c:402 txFreeMap+0x798/0xd50 fs/jfs/jfs_txnmgr.c:2534 txUpdateMap+0x342/0x9e0 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x47a/0xb70 fs/jfs/jfs_txnmgr.c:2732 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 Kernel Offset: disabled Rebooting in 86400 seconds..

The issue is caused when the value of lp becomes greater than CTLTREESIZE which is the max size of stree. Adding a simple check solves this issue.

Dave: As the function returns a void, good error handling would require a more intrusive code reorganization, so I modified Osama's patch at use WARN_ON_ONCE for lack of a cleaner option.

The patch is tested via syzbot.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

March 6, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59342822276f753e49d27ef5eebffbba990572b9
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42f433785f108893de0dd5260bafb85d7d51db03
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

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

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

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

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98f9537fe61b8382b3cc5dd97347531698517c56
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9862ec7ac1cbc6eb5ee4a045b5d5b8edbb2f7e68
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fe8b702125aeee6ce83f20092a2341446704e7b
generic

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a44065dd604972ec1fbcccbdc4a70d266a89cdd

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-22.04c (6.1.0.1035.36) @ jammy2026-05-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1084.80) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.106.116~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.106.106) @ jammy2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1043 (5.4.0-1043.47) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.35.35~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-tools-gke (4.15.0.1162.179~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-tools-azure (4.15.0.1177.192~14.04.1) @ trusty2026-05-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1061.61) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-hwe (4.15.0.1168.181~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.225.237~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.254.260) @ xenial2026-05-24ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1057.57) @ jammy2026-05-24ubuntu
linuxKernel @ 4.19.307—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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFixed inDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)4.19.316-1—
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)5.10.216-1~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)5.10.216-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)6.1.82-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.7.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.7.7-1—

Weakness Classification(1)

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

All Vendor Advisories

(14)

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 6× in last 7d / 29× 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 167 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-52604?
CVE-2023-52604 is a high vulnerability published on March 6, 2024. In the Linux kernel, the following vulnerability has been resolved: FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2867:6 index 196694 is out of range for type 's8[1365]' (aka 'signed char[1365]')…
When was CVE-2023-52604 disclosed?
CVE-2023-52604 was first published in the National Vulnerability Database on March 6, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52604 actively exploited?
CVE-2023-52604 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 83.4% of all scored CVEs.
What is the CVSS score of CVE-2023-52604?
CVE-2023-52604 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52604?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52604, 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-2023-52604

Explore →

Is Your Infrastructure Affected by CVE-2023-52604?

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

Start Free Scan →Browse All CVEs