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

CVE-2023-52604

Linux Linux, linux kernel

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 [inl...

CVSS
7.8
EPSS
0.25%
16.3% percentile
CISA KEV
Not listed
Published
2024.03.06
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

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 [inl...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e3e95c6850661c77e6dab079d9b5374a618ebb15, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 98f9537fe61b8382b3cc5dd97347531698517c56, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < de34de6e57bbbc868e4fcf9e98c76b3587cabb0b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6fe8b702125aeee6ce83f20092a2341446704e7b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 42f433785f108893de0dd5260bafb85d7d51db03, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6a44065dd604972ec1fbcccbdc4a70d266a89cdd, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 59342822276f753e49d27ef5eebffbba990572b9, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9862ec7ac1cbc6eb5ee4a045b5d5b8edbb2f7e68, >= 2.6.12, < 4.19.307, >= 4.20 < 5.4.269, >= 5.5 < 5.10.210, >= 5.11 < 5.15.149, >= 5.16 < 6.1.77, >= 6.2 < 6.6.16, >= 6.7 < 6.7.4
Fixed versions
4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4

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