CVE-2024-26698

一、漏洞信息
 漏洞编号：[CVE-2024-26698](https://nvd.nist.gov/vuln/detail/CVE-2024-26698)
 漏洞归属组件：[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
 CVSS V2.0分值：
 BaseScore：0.0 Low
 Vector：CVSS：2.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:hv_netvsc: Fix race condition between netvsc_probe and netvsc_removeIn commit ac5047671758 ( hv_netvsc: Disable NAPI before closing theVMBus channel ), napi_disable was getting called for all channels,including all subchannels without confirming if they are enabled or not.This caused hv_netvsc getting hung at napi_disable, when netvsc_probe()has finished running but nvdev->subchan_work has not started yet.netvsc_subchan_work() -> rndis_set_subchannel() has not created thesub-channels and because of that netvsc_sc_open() is not running.netvsc_remove() calls cancel_work_sync(&nvdev->subchan_work), for whichnetvsc_subchan_work did not run.netif_napi_add() sets the bit NAPI_STATE_SCHED because it ensures NAPIcannot be scheduled. Then netvsc_sc_open() -> napi_enable will clear theNAPIF_STATE_SCHED bit, so it can be scheduled. napi_disable() does theopposite.Now during netvsc_device_remove(), when napi_disable is called for thosesubchannels, napi_disable gets stuck on infinite msleep.This fix addresses this problem by ensuring that napi_disable() is notgetting called for non-enabled NAPI struct.But netif_napi_del() is still necessary for these non-enabled NAPI structfor cleanup purpose.Call trace:[ 654.559417] task:modprobe state:D stack: 0 pid: 2321 ppid: 1091 flags:0x00004002[ 654.568030] Call Trace:[ 654.571221] <TASK>[ 654.573790] __schedule+0x2d6/0x960[ 654.577733] schedule+0x69/0xf0[ 654.581214] schedule_timeout+0x87/0x140[ 654.585463] ? __bpf_trace_tick_stop+0x20/0x20[ 654.590291] msleep+0x2d/0x40[ 654.593625] napi_disable+0x2b/0x80[ 654.597437] netvsc_device_remove+0x8a/0x1f0 [hv_netvsc][ 654.603935] rndis_filter_device_remove+0x194/0x1c0 [hv_netvsc][ 654.611101] ? do_wait_intr+0xb0/0xb0[ 654.615753] netvsc_remove+0x7c/0x120 [hv_netvsc][ 654.621675] vmbus_remove+0x27/0x40 [hv_vmbus]
 漏洞公开时间：2024-04-03 23:15:52
 漏洞创建时间：2024-04-04 00:02:02
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2024-26698
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26698 | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-26698 | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518 | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11 | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2273117 | https://bugzilla.suse.com/show_bug.cgi?id=1222374 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024040338-CVE-2024-26698-36ac@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2273117 |
| ubuntu | https://git.kernel.org/linus/e0526ec5360a48ad3ab2e26e802b0532302a7e11 (6.8-rc3) | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-26698 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://ubuntu.com/security/notices/USN-6766-1 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-26698 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-26698 | https://ubuntu.com/security/CVE-2024-26698 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-26698 | https://ubuntu.com/security/CVE-2024-26698 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-26698 |
| ubuntu | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26698 | https://ubuntu.com/security/CVE-2024-26698 |

</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/e0526ec5360a48ad3ab2e26e802b0532302a7e11 | https://git.kernel.org/linus/ac5047671758ad4be9f93898247b3a8b6dfde4c7 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
 In the Linux kernel, the following vulnerability has been resolved:hv_netvsc: Fix race condition between netvsc_probe and netvsc_removeIn commit ac5047671758 ( hv_netvsc: Disable NAPI before closing theVMBus channel ), napi_disable was getting called for all channels,including all subchannels without confirming if they are enabled or not.This caused hv_netvsc getting hung at napi_disable, when netvsc_probe()has finished running but nvdev->subchan_work has not started yet.netvsc_subchan_work() -> rndis_set_subchannel() has not created thesub-channels and because of that netvsc_sc_open() is not running.netvsc_remove() calls cancel_work_sync(&nvdev->subchan_work), for whichnetvsc_subchan_work did not run.netif_napi_add() sets the bit NAPI_STATE_SCHED because it ensures NAPIcannot be scheduled. Then netvsc_sc_open() -> napi_enable will clear theNAPIF_STATE_SCHED bit, so it can be scheduled. napi_disable() does theopposite.Now during netvsc_device_remove(), when napi_disable is called for thosesubchannels, napi_disable gets stuck on infinite msleep.This fix addresses this problem by ensuring that napi_disable() is notgetting called for non-enabled NAPI struct.But netif_napi_del() is still necessary for these non-enabled NAPI structfor cleanup purpose.Call trace:[ 654.559417] task:modprobe state:D stack: 0 pid: 2321 ppid: 1091 flags:0x00004002[ 654.568030] Call Trace:[ 654.571221] <TASK>[ 654.573790] __schedule+0x2d6/0x960[ 654.577733] schedule+0x69/0xf0[ 654.581214] schedule_timeout+0x87/0x140[ 654.585463] ? __bpf_trace_tick_stop+0x20/0x20[ 654.590291] msleep+0x2d/0x40[ 654.593625] napi_disable+0x2b/0x80[ 654.597437] netvsc_device_remove+0x8a/0x1f0 [hv_netvsc][ 654.603935] rndis_filter_device_remove+0x194/0x1c0 [hv_netvsc][ 654.611101] ? do_wait_intr+0xb0/0xb0[ 654.615753] netvsc_remove+0x7c/0x120 [hv_netvsc][ 654.621675] vmbus_remove+0x27/0x40 [hv_vmbus] 
 openEuler评分：
 5.5
 Vector：CVSS：2.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
 1.openEuler-22.03-LTS(5.10.0):受影响
2.openEuler-22.03-LTS-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP2(5.10.0):受影响
4.openEuler-22.03-LTS-SP3(5.10.0):受影响
5.openEuler-20.03-LTS-SP1(4.19.90):不受影响
6.openEuler-20.03-LTS-SP4(4.19.90):不受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next(5.10.0):不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

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

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

@yangyingliang ,@gatieme ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 
**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-24.03-LTS:
10.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-24.03-LTS:
10.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-26698</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518>https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518</a> <a href=https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a>https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a</a> <a href=https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd>https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd</a> <a href=https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11>https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11</a> <a href=https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b>https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b</a> <a href=https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f>https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2024-26698</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-26698</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518>https://git.kernel.org/stable/c/48a8ccccffbae10c91d31fc872db5c31aba07518</a> <a href=https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a>https://git.kernel.org/stable/c/7656372ae190e54e8c8cf1039725a5ea59fdf84a</a> <a href=https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd>https://git.kernel.org/stable/c/0e8875de9dad12805ff66e92cd5edea6a421f1cd</a> <a href=https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11>https://git.kernel.org/stable/c/e0526ec5360a48ad3ab2e26e802b0532302a7e11</a> <a href=https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b>https://git.kernel.org/stable/c/22a77c0f5b8233237731df3288d067af51a2fd7b</a> <a href=https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f>https://git.kernel.org/stable/c/9ec807e7b6f5fcf9499f3baa69f254bb239a847f</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-26698</td><td></td><td></td><td></td></tr><tr><td>https://security-tracker.debian.org/tracker/CVE-2024-26698</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-26698

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

hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove

In commit ac5047671758 ("hv_netvsc: Disable NAPI before closing the
VMBus channel"), napi_disable was getting called for all channels,
including all subchannels without confirming if they are enabled or not.

This caused hv_netvsc getting hung at napi_disable, when netvsc_probe()
has finished running but nvdev->subchan_work has not started yet.
netvsc_subchan_work() -> rndis_set_subchannel() has not created the
sub-channels and because of that netvsc_sc_open() is not running.
netvsc_remove() calls cancel_work_sync(&nvdev->subchan_work), for which
netvsc_subchan_work did not run.

netif_napi_add() sets the bit NAPI_STATE_SCHED because it ensures NAPI
cannot be scheduled. Then netvsc_sc_open() -> napi_enable will clear the
NAPIF_STATE_SCHED bit, so it can be scheduled. napi_disable() does the
opposite.

Now during netvsc_device_remove(), when napi_disable is called for those
subchannels, napi_disable gets stuck on infinite msleep.

This fix addresses this problem by ensuring that napi_disable() is not
getting called for non-enabled NAPI struct.
But netif_napi_del() is still necessary for these non-enabled NAPI struct
for cleanup purpose.

Call trace:
[ 654.559417] task:modprobe state:D stack: 0 pid: 2321 ppid: 1091 flags:0x00004002
[ 654.568030] Call Trace:
[ 654.571221] <TASK>
[ 654.573790] __schedule+0x2d6/0x960
[ 654.577733] schedule+0x69/0xf0
[ 654.581214] schedule_timeout+0x87/0x140
[ 654.585463] ? __bpf_trace_tick_stop+0x20/0x20
[ 654.590291] msleep+0x2d/0x40
[ 654.593625] napi_disable+0x2b/0x80
[ 654.597437] netvsc_device_remove+0x8a/0x1f0 [hv_netvsc]
[ 654.603935] rndis_filter_device_remove+0x194/0x1c0 [hv_netvsc]
[ 654.611101] ? do_wait_intr+0xb0/0xb0
[ 654.615753] netvsc_remove+0x7c/0x120 [hv_netvsc]
[ 654.621675] vmbus_remove+0x27/0x40 [hv_vmbus]

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

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

===========================================================

src-openEuler/kernel

内容风险标识

评论 (13)

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

内容风险标识

CVE-2024-26698

评论 (13)

搜索帮助

src-openEuler/kernel