CVE-2024-35910

一、漏洞信息
 漏洞编号：[CVE-2024-35910](https://nvd.nist.gov/vuln/detail/CVE-2024-35910)
 漏洞归属组件：[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 Low
 Vector：CVSS：2.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:tcp: properly terminate timers for kernel socketsWe had various syzbot reports about tcp timers firing afterthe corresponding netns has been dismantled.Fortunately Josef Bacik could trigger the issue more often,and could test a patch I wrote two years ago.When TCP sockets are closed, we call inet_csk_clear_xmit_timers()to stop the timers.inet_csk_clear_xmit_timers() can be called from any context,including when socket lock is held.This is the reason it uses sk_stop_timer(), aka del_timer().This means that ongoing timers might finish much later.For user sockets, this is fine because each running timerholds a reference on the socket, and the user socket holdsa reference on the netns.For kernel sockets, we risk that the netns is freed beforetimer can complete, because kernel sockets do not holdreference on the netns.This patch adds inet_csk_clear_xmit_timers_sync() functionthat using sk_stop_timer_sync() to make sure all timersare terminated before the kernel socket is released.Modules using kernel sockets close them in their netns exit()handler.Also add sock_not_owned_by_me() helper to get LOCKDEPsupport : inet_csk_clear_xmit_timers_sync() must not be calledwhile socket lock is held.It is very possible we can revert in the future commit3a58f13a881e ( net: rds: acquire refcount on TCP sockets )which attempted to solve the issue in rds only.(net/smc/af_smc.c and net/mptcp/subflow.c have similar code)We probably can remove the check_net() tests fromtcp_out_of_resources() and __tcp_close() in the future.
 漏洞公开时间：2024-05-19 17:15:11
 漏洞创建时间：2024-05-19 17:45:23
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2024-35910
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35910 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-35910 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810 | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-35910.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1224489 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024051955-CVE-2024-35910-5f95@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2281641 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-35910 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/linus/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada (6.9-rc2) | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-35910 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-35910 | https://ubuntu.com/security/CVE-2024-35910 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-35910 | https://ubuntu.com/security/CVE-2024-35910 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-35910 |

</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/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada | https://git.kernel.org/linus/26abe14379f8e2fa3fd1bcf97c9a7ad9364886fe | ubuntu |
| linux |  | https://git.kernel.org/linus/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada | https://git.kernel.org/linus/8a68173691f036613e3d4e6bf8dc129d4a7bf383 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
      In the Linux kernel, the following vulnerability has been resolved:tcp: properly terminate timers for kernel socketsWe had various syzbot reports about tcp timers firing afterthe corresponding netns has been dismantled.Fortunately Josef Bacik could trigger the issue more often,and could test a patch I wrote two years ago.When TCP sockets are closed, we call inet_csk_clear_xmit_timers()to  stop  the timers.inet_csk_clear_xmit_timers() can be called from any context,including when socket lock is held.This is the reason it uses sk_stop_timer(), aka del_timer().This means that ongoing timers might finish much later.For user sockets, this is fine because each running timerholds a reference on the socket, and the user socket holdsa reference on the netns.For kernel sockets, we risk that the netns is freed beforetimer can complete, because kernel sockets do not holdreference on the netns.This patch adds inet_csk_clear_xmit_timers_sync() functionthat using sk_stop_timer_sync() to make sure all timersare terminated before the kernel socket is released.Modules using kernel sockets close them in their netns exit()handler.Also add sock_not_owned_by_me() helper to get LOCKDEPsupport : inet_csk_clear_xmit_timers_sync() must not be calledwhile socket lock is held.It is very possible we can revert in the future commit3a58f13a881e ( net: rds: acquire refcount on TCP sockets )which attempted to solve the issue in rds only.(net/smc/af_smc.c and net/mptcp/subflow.c have similar code)We probably can remove the check_net() tests fromtcp_out_of_resources() and __tcp_close() in the future.  
 openEuler评分：
  5.8
 Vector：CVSS：2.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
 受影响版本排查(受影响/不受影响)：
  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-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS(6.6.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):否

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

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**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):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:

修复是否涉及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):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:

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

<table><tr><th white-space: nowrap;>参考网址</th> <th white-space: nowrap;>关联pr</th> <th white-space: nowrap;>状态</th> <th white-space: nowrap;>补丁链接</th></tr><tr><td rowspan="1">https://nvd.nist.gov/vuln/detail/CVE-2024-35910</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87>https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87</a> <a href=https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810>https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810</a> <a href=https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada>https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada</a> <a href=https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a>https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a</a> <a href=https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de>https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de</a> <a href=https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50>https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50</a> <a href=https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f>https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f</a> <a href=https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4>https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2024-35910</td><td>None</td><td>None</td><td><a href=https://discourse.ubuntu.com/c/ubuntu-pro>https://discourse.ubuntu.com/c/ubuntu-pro</a></td></tr><tr><td rowspan="1">https://www.opencve.io/cve/CVE-2024-35910</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87>https://git.kernel.org/stable/c/c1ae4d1e76eacddaacb958b67cd942082f800c87</a> <a href=https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810>https://git.kernel.org/stable/c/e3e27d2b446deb1f643758a0c4731f5c22492810</a> <a href=https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada>https://git.kernel.org/stable/c/151c9c724d05d5b0dd8acd3e11cb69ef1f2dbada</a> <a href=https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a>https://git.kernel.org/stable/c/899265c1389fe022802aae73dbf13ee08837a35a</a> <a href=https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de>https://git.kernel.org/stable/c/91b243de910a9ac8476d40238ab3dbfeedd5b7de</a> <a href=https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50>https://git.kernel.org/stable/c/93f0133b9d589cc6e865f254ad9be3e9d8133f50</a> <a href=https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f>https://git.kernel.org/stable/c/44e62f5d35678686734afd47c6a421ad30772e7f</a> <a href=https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4>https://git.kernel.org/stable/c/2e43d8eba6edd1cf05a3a20fdd77688fa7ec16a4</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-35910</td><td></td><td></td><td></td></tr><tr><td>https://security-tracker.debian.org/tracker/CVE-2024-35910</td><td></td><td></td><td></td></tr></table>

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

CVE-2024-35910

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

tcp: properly terminate timers for kernel sockets

We had various syzbot reports about tcp timers firing after
the corresponding netns has been dismantled.

Fortunately Josef Bacik could trigger the issue more often,
and could test a patch I wrote two years ago.

When TCP sockets are closed, we call inet_csk_clear_xmit_timers()
to 'stop' the timers.

inet_csk_clear_xmit_timers() can be called from any context,
including when socket lock is held.
This is the reason it uses sk_stop_timer(), aka del_timer().
This means that ongoing timers might finish much later.

For user sockets, this is fine because each running timer
holds a reference on the socket, and the user socket holds
a reference on the netns.

For kernel sockets, we risk that the netns is freed before
timer can complete, because kernel sockets do not hold
reference on the netns.

This patch adds inet_csk_clear_xmit_timers_sync() function
that using sk_stop_timer_sync() to make sure all timers
are terminated before the kernel socket is released.
Modules using kernel sockets close them in their netns exit()
handler.

Also add sock_not_owned_by_me() helper to get LOCKDEP
support : inet_csk_clear_xmit_timers_sync() must not be called
while socket lock is held.

It is very possible we can revert in the future commit
3a58f13a881e ("net: rds: acquire refcount on TCP sockets")
which attempted to solve the issue in rds only.
(net/smc/af_smc.c and net/mptcp/subflow.c have similar code)

We probably can remove the check_net() tests from
tcp_out_of_resources() and __tcp_close() in the future.

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

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:受影响
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.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:不受影响
11.openEuler-24.03-LTS-Next:不受影响

修复是否涉及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:否
10.openEuler-24.03-LTS-Next:否
11.openEuler-22.03-LTS-SP4:否