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

CVE-2023-52599

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in diNewExt [Syz report] UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz-executor282 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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_hand...

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: jfs: fix array-index-out-of-bounds in diNewExt [Syz report] UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz-executor282 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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_hand...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f423528488e4f9606cef858eceea210bf1163f41, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < de6a91aed1e0b1a23e9c11e7d7557f088eeeb017, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6aa30020879042d46df9f747e4f0a486eea6fe98, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3537f92cd22c672db97fae6997481e678ad14641, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6996d43b14486f4a6655b10edc541ada1b580b4b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5a6660139195f5e2fbbda459eeecb8788f3885fe, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 49f9637aafa6e63ba686c13cb8549bf5e6920402, >= 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