CVE-2023-52599: jfs: fix array-index-out-of-bounds in diNewExt
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/jfsimap.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> dumpstack lib/dumpstack.c:88 [inline] dumpstacklvl+0x1e7/0x2d0 lib/dumpstack.c:106 ubsanepilogue lib/ubsan.c:217 [inline] ubsanhandleoutofbounds+0x11c/0x150 lib/ubsan.c:348 diNewExt+0x3cf3/0x4000 fs/jfs/jfsimap.c:2360 diAllocExt fs/jfs/jfsimap.c:1949 [inline] diAllocAG+0xbe8/0x1e50 fs/jfs/jfsimap.c:1666 diAlloc+0x1d3/0x1760 fs/jfs/jfsimap.c:1587 ialloc+0x8f/0x900 fs/jfs/jfsinode.c:56 jfsmkdir+0x1c5/0xb90 fs/jfs/namei.c:225 vfsmkdir+0x2f1/0x4b0 fs/namei.c:4106 domkdirat+0x264/0x3a0 fs/namei.c:4129 dosysmkdir fs/namei.c:4149 [inline] sesysmkdir fs/namei.c:4147 [inline] x64sysmkdir+0x6e/0x80 fs/namei.c:4147 dosyscallx64 arch/x86/entry/common.c:51 [inline] dosyscall64+0x45/0x110 arch/x86/entry/common.c:82 entrySYSCALL64afterhwframe+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 ORIGRAX: 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).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52599?
CVE-2023-52599 has a moderate severity level due to the potential for array-index-out-of-bounds, which could lead to unexpected behavior in the Linux kernel.
How do I fix CVE-2023-52599?
To fix CVE-2023-52599, update to the latest version of the Linux kernel that includes the patch for this vulnerability.
What versions of the Linux kernel are affected by CVE-2023-52599?
CVE-2023-52599 affects Linux kernel versions from 4.19.0 up to but not including 5.16.0, as well as several specific releases thereafter.
What type of vulnerability is CVE-2023-52599?
CVE-2023-52599 is classified as an array-index-out-of-bounds vulnerability in the Linux kernel.
What is the potential impact of CVE-2023-52599?
The potential impact of CVE-2023-52599 includes system instability or crashes if exploited, affecting the reliability of systems running the vulnerable kernel versions.