Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0e8875de9dad12805ff66e92cd5edea6a421f1cd, 22a77c0f5b8233237731df3288d067af51a2fd7b, 48a8ccccffbae10c91d31fc872db5c31aba07518.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0e8875de9dad12805ff66e92cd5edea6a421f1cd, 22a77c0f5b8233237731df3288d067af51a2fd7b, 48a8ccccffbae10c91d31fc872db5c31aba07518 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Apr 3, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26698

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.149
  • linux linux kernel5.16 and later · before 6.1.79
  • linux linux kernel5.8 and later · before 5.10.210
  • linux linux kernel6.7 and later · before 6.7.6
  • linux linux kernel6.2 and later · before 6.6.18
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.8affected
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before 9ec807e7b6f5fcf9499f3baa69f254bb239a847faffected · git
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before 7656372ae190e54e8c8cf1039725a5ea59fdf84aaffected · git
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before 48a8ccccffbae10c91d31fc872db5c31aba07518affected · git
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before 22a77c0f5b8233237731df3288d067af51a2fd7baffected · git
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before 0e8875de9dad12805ff66e92cd5edea6a421f1cdaffected · git
    • ac5047671758ad4be9f93898247b3a8b6dfde4c7 and later · before e0526ec5360a48ad3ab2e26e802b0532302a7e11affected · git
    • before 5.8not affected · semver
    • 5.10.210 and later · up to and including 5.10.*not affected · semver
    • 5.15.149 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseosperf-debuginfobefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6
Red Hat:rhel_aus:8.6::baseospython3-perfbefore 0:4.18.0-372.121.1.el8_60:4.18.0-372.121.1.el8_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26696Apr 3, 2024 · nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()
    22Monitor
  • ← EarlierCVE-2024-26697Apr 3, 2024 · nilfs2: fix data corruption in dsync block recovery for small block sizes
    22Monitor
  • Later →CVE-2024-26699Apr 3, 2024 · drm/amd/display: Fix array-index-out-of-bounds in dcn35_clkmgr
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e8875de9dad12805ff66e92cd5edea6a421f1cdVendor (CNA)
Linux Linux22a77c0f5b8233237731df3288d067af51a2fd7bVendor (CNA)
Linux Linux48a8ccccffbae10c91d31fc872db5c31aba07518Vendor (CNA)
Linux Linux7656372ae190e54e8c8cf1039725a5ea59fdf84aVendor (CNA)
Linux Linux9ec807e7b6f5fcf9499f3baa69f254bb239a847fVendor (CNA)
Linux Linuxe0526ec5360a48ad3ab2e26e802b0532302a7e11Vendor (CNA)
almalinux:bpftool4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.75.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records