CVE-2024-36905

一、漏洞信息
 漏洞编号：[CVE-2024-36905](https://nvd.nist.gov/vuln/detail/CVE-2024-36905)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/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,6.6.0
 CVSS V2.0分值：
  BaseScore：0.0 None
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV socketsTCP_SYN_RECV state is really special, it is only used bycross-syn connections, mostly used by fuzzers.In the following crash [1], syzbot managed to trigger a divideby zero in tcp_rcv_space_adjust()A socket makes the following state transitions,without ever calling tcp_init_transfer(),meaning tcp_init_buffer_space() is also not called.         TCP_CLOSEconnect()         TCP_SYN_SENT         TCP_SYN_RECVshutdown() -> tcp_shutdown(sk, SEND_SHUTDOWN)         TCP_FIN_WAIT1To fix this issue, change tcp_shutdown() to notperform a TCP_SYN_RECV -> TCP_FIN_WAIT1 transition,which makes no sense anyway.When tcp_rcv_state_process() later changes socket statefrom TCP_SYN_RECV to TCP_ESTABLISH, then look atsk->sk_shutdown to finally enter TCP_FIN_WAIT1 state,and send a FIN packet from a sane socket state.This means tcp_send_fin() can now be called from BHcontext, and must use GFP_ATOMIC allocations.[1]divide error: 0000 [#1] PREEMPT SMP KASAN NOPTICPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767Code: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 <48> f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48RSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246RAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000RBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7R10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30R13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2daFS:  00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0Call Trace: <TASK>  tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513  tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578  inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680  sock_recvmsg_nosec net/socket.c:1046 [inline]  sock_recvmsg+0x109/0x280 net/socket.c:1068  ____sys_recvmsg+0x1db/0x470 net/socket.c:2803  ___sys_recvmsg net/socket.c:2845 [inline]  do_recvmmsg+0x474/0xae0 net/socket.c:2939  __sys_recvmmsg net/socket.c:3018 [inline]  __do_sys_recvmmsg net/socket.c:3041 [inline]  __se_sys_recvmmsg net/socket.c:3034 [inline]  __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7fRIP: 0033:0x7faeb6363db9Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012bRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9RDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001cR10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
 漏洞公开时间：2024-05-31 00:15:14
 漏洞创建时间：2024-06-01 01:30:37
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-36905
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2552c9d9440f8e7a2ed0660911ff00f25b90a0a4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/34e41a031fd7523bf1cd00a2adca2370aebea270 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3fe4ef0568a48369b1891395d13ac593b1ba41b1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/413c33b9f3bc36fdf719690a78824db9f88a9485 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/94062790aedb505bdda209b10bea47b294d6394f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/cbf232ba11bc86a5281b4f00e1151349ef4d45cf |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ed5e279b69e007ce6c0fe82a5a534c1b19783214 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f47d0d32fa94e815fdd78b8b88684873e67939f4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://lists.debian.org/debian-lts-announce/2024/06/msg00019.html |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36905 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36905.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/34e41a031fd7523bf1cd00a2adca2370aebea270 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/ed5e279b69e007ce6c0fe82a5a534c1b19783214 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/413c33b9f3bc36fdf719690a78824db9f88a9485 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/2552c9d9440f8e7a2ed0660911ff00f25b90a0a4 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/3fe4ef0568a48369b1891395d13ac593b1ba41b1 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/f47d0d32fa94e815fdd78b8b88684873e67939f4 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/cbf232ba11bc86a5281b4f00e1151349ef4d45cf | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://git.kernel.org/stable/c/94062790aedb505bdda209b10bea47b294d6394f | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-36905 | https://bugzilla.suse.com/show_bug.cgi?id=1225742 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024053036-CVE-2024-36905-5884@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2284539 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-36905 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/linus/94062790aedb505bdda209b10bea47b294d6394f (6.9) | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/34e41a031fd7523bf1cd00a2adca2370aebea270 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/ed5e279b69e007ce6c0fe82a5a534c1b19783214 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/413c33b9f3bc36fdf719690a78824db9f88a9485 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/2552c9d9440f8e7a2ed0660911ff00f25b90a0a4 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/3fe4ef0568a48369b1891395d13ac593b1ba41b1 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/f47d0d32fa94e815fdd78b8b88684873e67939f4 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/cbf232ba11bc86a5281b4f00e1151349ef4d45cf | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://git.kernel.org/stable/c/94062790aedb505bdda209b10bea47b294d6394f | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-36905 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-36905 | https://ubuntu.com/security/CVE-2024-36905 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-36905 | https://ubuntu.com/security/CVE-2024-36905 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-36905 |
| amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2024-36905 | https://explore.alas.aws.amazon.com/CVE-2024-36905.html |
| amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36905 | https://explore.alas.aws.amazon.com/CVE-2024-36905.html |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

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

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV socketsTCP_SYN_RECV state is really special, it is only used bycross-syn connections, mostly used by fuzzers.In the following crash [1], syzbot managed to trigger a divideby zero in tcp_rcv_space_adjust()A socket makes the following state transitions,without ever calling tcp_init_transfer(),meaning tcp_init_buffer_space() is also not called.         TCP_CLOSEconnect()         TCP_SYN_SENT         TCP_SYN_RECVshutdown() -> tcp_shutdown(sk, SEND_SHUTDOWN)         TCP_FIN_WAIT1To fix this issue, change tcp_shutdown() to notperform a TCP_SYN_RECV -> TCP_FIN_WAIT1 transition,which makes no sense anyway.When tcp_rcv_state_process() later changes socket statefrom TCP_SYN_RECV to TCP_ESTABLISH, then look atsk->sk_shutdown to finally enter TCP_FIN_WAIT1 state,and send a FIN packet from a sane socket state.This means tcp_send_fin() can now be called from BHcontext, and must use GFP_ATOMIC allocations.[1]divide error: 0000 [#1] PREEMPT SMP KASAN NOPTICPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767Code: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 <48> f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48RSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246RAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000RBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7R10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30R13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2daFS:  00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0Call Trace: <TASK>  tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513  tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578  inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680  sock_recvmsg_nosec net/socket.c:1046 [inline]  sock_recvmsg+0x109/0x280 net/socket.c:1068  ____sys_recvmsg+0x1db/0x470 net/socket.c:2803  ___sys_recvmsg net/socket.c:2845 [inline]  do_recvmmsg+0x474/0xae0 net/socket.c:2939  __sys_recvmmsg net/socket.c:3018 [inline]  __do_sys_recvmmsg net/socket.c:3041 [inline]  __se_sys_recvmmsg net/socket.c:3034 [inline]  __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7fRIP: 0033:0x7faeb6363db9Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48RSP: 002b:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012bRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9RDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001cR10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
 openEuler评分：
  5.6
 Vector：CVSS：3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (56)

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

Content Risk Flag

CVE-2024-36905

Comments (56)

Search

src-openEuler/kernel
Closed