Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-52604 — kernel

🟠 CVSS 7.8 — High ✅ No Known Exploit NVD
7.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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:

<TASK>

__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

</TASK>

================================================================================

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:

<TASK>

__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

</TASK>

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2023-52604 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.7.4)
  • linux-kernel (from 6.7 up to 6.7.4)

Timeline and source

Published on 6 March 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
lists.debian.org (Web)
lists.debian.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2023-52604 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity High
CVSS Score 7.8
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-03-06
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.7.4
linux-kernel 6.7 6.7.4

References

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2023-52604 is rated CVSS 7.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2023
✓