CVE-2023-53485

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-01. 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

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:

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev

Syzkaller reported the following issue:

UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:1965:6 index -84 is out of range for type 's8[341]' (aka 'signed char[341]') CPU: 1 PID: 4995 Comm: syz-executor146 Not tainted 6.4.0-rc6-syzkaller-00037-gb6dad5178cea #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/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 dbAllocDmapLev+0x3e5/0x430 fs/jfs/jfs_dmap.c:1965 dbAllocCtl+0x113/0x920 fs/jfs/jfs_dmap.c:1809 dbAllocAG+0x28f/0x10b0 fs/jfs/jfs_dmap.c:1350 dbAlloc+0x658/0xca0 fs/jfs/jfs_dmap.c:874 dtSplitUp fs/jfs/jfs_dtree.c:974 [inline] dtInsert+0xda7/0x6b00 fs/jfs/jfs_dtree.c:863 jfs_create+0x7b6/0xbb0 fs/jfs/namei.c:137 lookup_open fs/namei.c:3492 [inline] open_last_lookups fs/namei.c:3560 [inline] path_openat+0x13df/0x3170 fs/namei.c:3788 do_filp_open+0x234/0x490 fs/namei.c:3818 do_sys_openat2+0x13f/0x500 fs/open.c:1356 do_sys_open fs/open.c:1372 [inline] __do_sys_openat fs/open.c:1388 [inline] __se_sys_openat fs/open.c:1383 [inline] __x64_sys_openat+0x247/0x290 fs/open.c:1383 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1f4e33f7e9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc21129578 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1f4e33f7e9 RDX: 000000000000275a RSI: 0000000020000040 RDI: 00000000ffffff9c RBP: 00007f1f4e2ff080 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1f4e2ff110 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

The bug occurs when the dbAllocDmapLev()function attempts to access dp->tree.stree[leafidx + LEAFIND] while the leafidx value is negative.

To rectify this, the patch introduces a safeguard within the dbAllocDmapLev() function. A check has been added to verify if leafidx is negative. If it is, the function immediately returns an I/O error, preventing any further execution that could potentially cause harm.

Tested via syzbot.

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

Published

October 1, 2025

Last Modified

August 5, 2026

Advisory Details (8)

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

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e302336d5ca1767a06beee7596a72d3bdc8d983
generic

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39f6292d75959e8accac0b3e24090094ba0824e9
generic

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/911b48eec45152822bccf45cd3563b48256b1520
generic

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53b0a362aca2583729e8ca2936ca657ff3247d88
generic

fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.14.324osv

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 ... 5.10.92-2 (34 versions)5.10.197-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)6.1.52-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.4.11-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.4.11-1

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2023-53485?
CVE-2023-53485 is a high vulnerability published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:1965:6 index -84 is out of range for type 's8[341]' (aka 'signed…
When was CVE-2023-53485 disclosed?
CVE-2023-53485 was first published in the National Vulnerability Database on October 1, 2025, 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-53485 actively exploited?
CVE-2023-53485 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 91.5% of all scored CVEs.
What is the CVSS score of CVE-2023-53485?
CVE-2023-53485 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53485?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53485, 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-53485

Explore →

Is Your Infrastructure Affected by CVE-2023-53485?

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