CVE-2023-52603

一、漏洞信息
漏洞编号：CVE-2023-52603
漏洞归属组件：kernel
漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0
CVSS V2.0分值：
BaseScore：0.0 Low
Vector：CVSS：2.0/
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:UBSAN: array-index-out-of-bounds in dtSplitRootSyzkaller reported the following issue:oop0: detected capacity change from 0 to 32768UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9index -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 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcdRIP: 0033:0x7fcdc0113fd9Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1.The check to break the loop when fsi value becomes -1 is presentbut syzbot was able to produce value less than -1 which cause the error.This patch simply add the change for the values less than 0.The patch is tested via syzbot.
漏洞公开时间：2024-03-06 15:15:11
漏洞创建时间：2024-03-06 21:54:23
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2023-52603

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52603	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2023-52603	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60	https://bugzilla.suse.com/show_bug.cgi?id=1221066
suse_bugzilla	https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39	https://bugzilla.suse.com/show_bug.cgi?id=1221066
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52603-e47b@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2268299
ubuntu	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52603	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/linus/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16 (6.8-rc1)	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://ubuntu.com/security/notices/USN-6688-1	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://nvd.nist.gov/vuln/detail/CVE-2023-52603	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://launchpad.net/bugs/cve/CVE-2023-52603	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://security-tracker.debian.org/tracker/CVE-2023-52603	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2023-52603	https://ubuntu.com/security/CVE-2023-52603
ubuntu	https://bugzilla.suse.com/show_bug.cgi?id=1221066	https://ubuntu.com/security/CVE-2023-52603
debian		https://security-tracker.debian.org/tracker/CVE-2023-52603
cve_search		https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af
cve_search		https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07
cve_search		https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8
cve_search		https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39
cve_search		https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60
cve_search		https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f
cve_search		https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2
cve_search		https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux		https://git.kernel.org/linus/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16	https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2	ubuntu

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:UBSAN: array-index-out-of-bounds in dtSplitRootSyzkaller reported the following issue:oop0: detected capacity change from 0 to 32768UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9index -2 is out of range for type _x27;struct dtslot [128]_x27;CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcdRIP: 0033:0x7fcdc0113fd9Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 </TASK>The issue is caused when the value of fsi becomes less than -1.The check to break the loop when fsi value becomes -1 is presentbut syzbot was able to produce value less than -1 which cause the error.This patch simply add the change for the values less than 0.The patch is tested via syzbot.
openEuler评分：
7.1
Vector：CVSS：2.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS(5.10.0):受影响
4.openEuler-22.03-LTS-SP1(5.10.0):受影响
5.openEuler-22.03-LTS-SP2(5.10.0):受影响
6.openEuler-22.03-LTS-SP3(5.10.0):受影响
7.openEuler-22.03-LTS-Next(5.10.0):受影响
8.master(6.1.0):不受影响
9.openEuler-24.03-LTS:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS(5.10.0):否
4.openEuler-22.03-LTS-SP1(5.10.0):否
5.openEuler-22.03-LTS-SP2(5.10.0):否
6.openEuler-22.03-LTS-SP3(5.10.0):否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next(5.10.0):否
9.openEuler-24.03-LTS:否

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1392

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@YangYingliang ,@成坚 (CHENG Jian) ,@jiaoff ,@AlexGuo ,@hanjun-guo ,@woqidaideshi ,@Jackie Liu ,@Zhang Yi ,@colyli ,@ThunderTown ,@htforge ,@Chiqijun ,@冷嘲啊 ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@Kefeng ,@SuperSix173 ,@WangShaoBo ,@Zheng Zucheng
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):

修复是否涉及abi变化(是/否)：
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):

issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2023-52603	None	None	https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8 https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60 https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07 https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16 https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2 https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39
https://ubuntu.com/security/CVE-2023-52603
https://www.opencve.io/cve/CVE-2023-52603	None	None	https://git.kernel.org/stable/c/e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af https://git.kernel.org/stable/c/7aa33854477d9c346f5560a1a1fcb3fe7783e2a8 https://git.kernel.org/stable/c/e4cbc857d75d4e22a1f75446e7480b1f305d8d60 https://git.kernel.org/stable/c/fd3486a893778770557649fe28afa5e463d4ed07 https://git.kernel.org/stable/c/edff092a59260bf0b0a2eba219cb3da6372c2f9f https://git.kernel.org/stable/c/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16 https://git.kernel.org/stable/c/6e2902ecc77e9760a9fc447f56d598383e2372d2 https://git.kernel.org/stable/c/e4ce01c25ccbea02a09a5291c21749b1fc358e39
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2023-52603
https://security-tracker.debian.org/tracker/CVE-2023-52603	None	None	https://git.kernel.org/linus/27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

@ci-robot 请确认分支: master,openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP2,openEuler-22.03-LTS-SP3,openEuler-24.03-LTS 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.

CVE-2023-52603

影响性分析说明：
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 _x27;struct dtslot [128]_x27;
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_stack.c:106
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283
dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971
dtSplitUp fs/jfs/jfs_dtree.c:985 [inline]
dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863
jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270
vfs_mkdir+0x3b3/0x590 fs/namei.c:4013
do_mkdirat+0x279/0x550 fs/namei.c:4038
__do_sys_mkdirat fs/namei.c:4053 [inline]
__se_sys_mkdirat fs/namei.c:4051 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fcdc0113fd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9
RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003
RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0
R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000
R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000
</TASK>

The issue is caused when the value of fsi becomes less than -1.
The check to break the loop when fsi value becomes -1 is present
but syzbot was able to produce value less than -1 which cause the error.
This patch simply add the change for the values less than 0.

The patch is tested via syzbot.

openEuler评分:(评分和向量)
7.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:受影响
6.openEuler-22.03-LTS-SP3:受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next:受影响
9.openEuler-24.03-LTS:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否

@ 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	需分析	内容
已分析	1.影响性分析说明	In the Linux kernel, the following vulnerability has been resolved:UBSAN: array-index-out-of-bounds in dtSplitRootSyzkaller reported the following issue:oop0: detected capacity change from 0 to 32768UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9index -2 is out of range for type _x27;struct dtslot [128]_x27;CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcdRIP: 0033:0x7fcdc0113fd9Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 </TASK>The issue is caused when the value of fsi becomes less than -1.The check to break the loop when fsi value becomes -1 is presentbut syzbot was able to produce value less than -1 which cause the error.This patch simply add the change for the values less than 0.The patch is tested via syzbot.
已分析	2.openEulerScore	7.1
已分析	3.openEulerVector	AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
已分析	4.受影响版本排查	openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP2:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-Next:受影响,master:不受影响,openEuler-24.03-LTS:不受影响
已分析	5.修复是否涉及abi变化	openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

@成坚 (CHENG Jian) ,@Xie XiuQi ,@YangYingliang ,@pi3orama ,@jiaoff ,@zhangjialin
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #I96G93:CVE-2023-52603
受影响分支: openEuler-20.03-LTS-SP1/openEuler-20.03-LTS-SP4/openEuler-22.03-LTS-Next/openEuler-22.03-LTS-SP3
具体操作参考: https://gitee.com/help/articles/4142

@成坚 (CHENG Jian) ,@Xie XiuQi ,@YangYingliang ,@pi3orama ,@jiaoff ,@zhangjialin
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #I96G93:CVE-2023-52603
受影响分支: openEuler-22.03-LTS-Next/openEuler-22.03-LTS-SP3/openEuler-20.03-LTS-SP1/openEuler-20.03-LTS-SP4
具体操作参考: https://gitee.com/help/articles/4142

@成坚 (CHENG Jian) ,@Xie XiuQi ,@YangYingliang ,@pi3orama ,@jiaoff ,@zhangjialin
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #I96G93:CVE-2023-52603
受影响分支: openEuler-20.03-LTS-SP1/openEuler-20.03-LTS-SP4
具体操作参考: https://gitee.com/help/articles/4142

@成坚 (CHENG Jian) ,@Xie XiuQi ,@YangYingliang ,@pi3orama ,@jiaoff ,@hongrongxuan
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #I96G93:CVE-2023-52603
受影响分支: openEuler-20.03-LTS-SP1
具体操作参考: https://gitee.com/help/articles/4142

src-openEuler / kernel

内容风险标识

评论 (13)

src-openEuler / kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2023-52603

评论 (13)

搜索帮助

src-openEuler / kernel