SECUFOCUSNOW
Home›CVE index›CVE-2023-53485
Review reviewHigh

CVE-2023-53485

Linux Linux, linux kernel

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: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 u...

CVSS
7.8
EPSS
0.17%
6.99% percentile
CISA KEV
Not listed
Published
2025.10.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.17%
Technical severityCVSS 7.8

Vulnerability overview

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: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 u...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0d9e678a82915633b99603f744e7735d1a673d72, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 53b0a362aca2583729e8ca2936ca657ff3247d88, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6e7d9d76e5654bcdd3cdb7c9441a8113428ecebb, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 911b48eec45152822bccf45cd3563b48256b1520, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 39f6292d75959e8accac0b3e24090094ba0824e9, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bdf07ab1595b613b03f32dbb5cb379edfa1a7334, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f2af019091f904ca08b3572ab0111238ad6d17b3, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4e302336d5ca1767a06beee7596a72d3bdc8d983, >= 2.6.12, >= 2.6.12.1 < 4.14.324, >= 4.15 < 4.19.293, >= 4.20 < 5.4.255, >= 5.5 < 5.10.192, >= 5.11 < 5.15.123, >= 5.16 < 6.1.42, >= 6.2 < 6.4.7, 2.6.12
Fixed versions
4.14.324, 4.19.293, 5.4.255, 5.10.192, 5.15.123, 6.1.42, 6.4.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-129
CVE-2023-53485 — Linux Linux, linux kernel | SECUFOCUS NOW