[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2024-26698":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":21,"related":22,"reserved_at":9,"published_at":23,"modified_at":24,"state":9,"summary":25,"references_raw":27,"kevs":34,"epss":9,"epss_history":35,"metrics":36,"affected":43},"DEBIAN-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]  \u003CTASK> [  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]",null,[],[],[],[14],{"_key":15},"CVE-2024-26698",[17,19],{"_key":18},"DLA-3842-1",{"_key":20},"DSA-5681-1",[],[],"2024-04-03T15:15:52.933Z","2026-04-28T20:27:39.447599Z",{"cisa_kev":26,"cisa_ransomware":26,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[28],{"url":29,"sources":30,"tags":32},"https://security-tracker.debian.org/tracker/CVE-2024-26698",[31],"osv_debian",[33],"Advisory",[],[],[37],{"source":31,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":38,"cvss_v4_0":9},{"baseScore":39,"baseSeverity":9,"vectorString":40,"impactScore":41,"exploitabilityScore":42},4.7,"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",6,2.6,[44],{"ecosystem":45,"name":46,"vendor":47,"product":46,"cpe_part":9,"purl_type":48,"purl_namespace":47,"purl_name":46,"source":9,"versions":49},"Debian","linux","debian","deb",[50,56,59,62],{"version":51,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":55,"fixed_in":9},"lt5_10_216_1",true,"ecosystem","5.10.216-1","excluding",{"version":57,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":58,"version_end_type":55,"fixed_in":9},"lt6_1_82_1","6.1.82-1",{"version":60,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":61,"version_end_type":55,"fixed_in":9},"lt6_7_7_1","6.7.7-1",{"version":60,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":61,"version_end_type":55,"fixed_in":9}]