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

CVE-2023-52603

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump...

CVSS
7.8
EPSS
0.29%
21.1% 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.29%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fd3486a893778770557649fe28afa5e463d4ed07, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7aa33854477d9c346f5560a1a1fcb3fe7783e2a8, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e4ce01c25ccbea02a09a5291c21749b1fc358e39, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e4cbc857d75d4e22a1f75446e7480b1f305d8d60, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < edff092a59260bf0b0a2eba219cb3da6372c2f9f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6e2902ecc77e9760a9fc447f56d598383e2372d2, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16, >= 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