CyberSecBulletin
CVE-2023-52599NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2023-52599 is a high-severity improper validation of array index vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions f423528488e4f9606cef858eceea210bf1163f41, de6a91aed1e0b1a23e9c11e7d7557f088eeeb017, e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to f423528488e4f9606cef858eceea210bf1163f41 or de6a91aed1e0b1a23e9c11e7d7557f088eeeb017 or e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e or 6aa30020879042d46df9f747e4f0a486eea6fe98, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.307 or 5.4.269 or 5.10.210 or 5.15.149, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, f423528488e4f9606cef858eceea210bf1163f41; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, de6a91aed1e0b1a23e9c11e7d7557f088eeeb017; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 6aa30020879042d46df9f747e4f0a486eea6fe98; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 3537f92cd22c672db97fae6997481e678ad14641; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 6996d43b14486f4a6655b10edc541ada1b580b4b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 5a6660139195f5e2fbbda459eeecb8788f3885fe; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 49f9637aafa6e63ba686c13cb8549bf5e6920402; and 1 more rangesf423528488e4f9606cef858eceea210bf1163f41, de6a91aed1e0b1a23e9c11e7d7557f088eeeb017, e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e, 6aa30020879042d46df9f747e4f0a486eea6fe98, 3537f92cd22c672db97fae6997481e678ad14641, 6996d43b14486f4a6655b10edc541ada1b580b4b
LinuxLinux Kernelbefore 4.19.307; 4.20 up to, but not including, 5.4.269; 5.5 up to, but not including, 5.10.210; 5.11 up to, but not including, 5.15.149; 5.16 up to, but not including, 6.1.77; 6.2 up to, but not including, 6.6.16; 6.7 up to, but not including, 6.7.44.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

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_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 diNewExt+0x3cf3/0x4000 fs/jfs/jfs_imap.c:2360 diAllocExt fs/jfs/jfs_imap.c:1949 [inline] diAllocAG+0xbe8/0x1e50 fs/jfs/jfs_imap.c:1666 diAlloc+0x1d3/0x1760 fs/jfs/jfs_imap.c:1587 ialloc+0x8f/0x900 fs/jfs/jfs_inode.c:56 jfs_mkdir+0x1c5/0xb90 fs/jfs/namei.c:225 vfs_mkdir+0x2f1/0x4b0 fs/namei.c:4106 do_mkdirat+0x264/0x3a0 fs/namei.c:4129 __do_sys_mkdir fs/namei.c:4149 [inline] __se_sys_mkdir fs/namei.c:4147 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4147 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7fcb7e6a0b57 Code: ff ff 77 07 31 c0 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd83023038 EFLAGS: 00000286 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fcb7e6a0b57 RDX: 00000000000a1020 RSI: 00000000000001ff RDI: 0000000020000140 RBP: 0000000020000140 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffd830230d0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [Analysis] When the agstart is too large, it can cause agno overflow. [Fix] After obtaining agno, if the value is invalid, exit the subsequent process. Modified the test from agno > MAXAG to agno >= MAXAG based on linux-next report by kernel test robot (Dan Carpenter).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Array Index

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How developers prevent this class of flaw

  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
  • Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.

More Improper Validation of Array Index vulnerabilities (CWE-129)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.