Vulnerability · Published Apr 3, 2024 · Assigned by Linux

CVE-2024-26698hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove

Medium 4.7

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)4.7Medium
Exploit odds (30 days)0.2%top 92.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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]

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.82-1DEBIAN-CVE-2024-26698
Debian:13linux6.7.7-1DEBIAN-CVE-2024-26698
Debian:14linux6.7.7-1DEBIAN-CVE-2024-26698
Ubuntu:22.04:LTSlinux5.15.0-106.116UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-aws5.15.0-1061.67UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-aws-6.56.5.0-1023.23~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-aws-6.56.5.0-1023.23~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-azure5.15.0-1056.64UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1015.15~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1024.25~22.04.1USN-6895-2
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1056.64.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gcp5.15.0-1059.67UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1024.26~22.04.1USN-6895-2
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1024.26~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gke5.15.0-1058.63UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1044.51UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-44.44~22.04.1USN-6900-1
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-44.44~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-ibm5.15.0-1054.57UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1057.63UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-kvm5.15.0-1058.63UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-106.116UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-44.44.1~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-44.44.1~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1054.55UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1023.24USN-6895-1
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1023.24UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1026.26UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1015.15UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1027.28USN-6895-4
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1027.28UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oracle5.15.0-1059.65UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1026.26~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1026.26~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-raspi5.15.0-1054.57UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1017.18~22.04.1USN-6895-3
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1017.18~22.04.1UBUNTU-CVE-2024-26698
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1030.34UBUNTU-CVE-2024-26698

Affected products (as reported)

VendorProductVersions
Linux Linux ac5047671758ad4be9f93898247b3a8b6dfde4c7 – before 9ec807e7b6f5fcf9499f3baa69f254bb239a847fac5047671758ad4be9f93898247b3a8b6dfde4c7 – before 7656372ae190e54e8c8cf1039725a5ea59fdf84aac5047671758ad4be9f93898247b3a8b6dfde4c7 – before 48a8ccccffbae10c91d31fc872db5c31aba07518ac5047671758ad4be9f93898247b3a8b6dfde4c7 – before 22a77c0f5b8233237731df3288d067af51a2fd7bac5047671758ad4be9f93898247b3a8b6dfde4c7 – before 0e8875de9dad12805ff66e92cd5edea6a421f1cdac5047671758ad4be9f93898247b3a8b6dfde4c7 – before e0526ec5360a48ad3ab2e26e802b0532302a7e11
Linux Linux 5.8

References