CVE Intelligence
Medium

CVE-2024-26820 — hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed

In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed If hv_netvsc driver is unloaded and reloaded, the NET_DEVICE_REGISTER handler cannot perform VF register successfully as the register call is received before netvsc_probe is finished. This is because we register register_netdevice_notifier() very early( even before vmbus_driver_register()). To fix this, we try to register each such matching VF( if it is visible as a netdevice) at the end of netvsc_probe.

Published Apr 17, 2024 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.24%
ahead of 14% of scored CVEs · Oct 15, 2026
Affects
Debian
Debian Linux and 2 more
CVSS base
5.5
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 10.0 Vulnerable NIST National Vulnerability Database
Linux Linux ≥ ff6c130e48a79c826cbc2427bd8b34a7592460cc and < 5b10a88f64c0315cfdef45de0aaaa4eef57de0b7version 6.7≥ 6.6.4 and < 6.6.18≥ 6.1.65 and < 6.1.79≥ 5.15.141 and < 5.15.152≥ 5.10.203 and < 5.10.213≥ 5.4.263 and < 5.4.272≥ 4.19.301 and < 4.19.310
and 7 more ≥ 85520856466ed6bc3b1ccb013cddac70ceb437db and < 9cae43da9867412f8bd09aee5c8a8dc5e8dc3dc2≥ 85520856466ed6bc3b1ccb013cddac70ceb437db and < 4d29a58d96a78728cb01ee29ed70dc4bd642f135≥ 7350c460f7f48a8653a15c5c90fc9070aaa29535 and < a71302c8638939c45e4ba5a99ea438185fd3f418≥ 5dd83db613be8e5c5d30efed7f42780e9eb18380 and < 309ef7de5d840e17607e7d65cbf297c0564433ef≥ 97683466e24c801ee4e865ce90ac7e355db2da59 and < b6d46f306b3964d05055ddaa96b58cd8bd3a472c≥ 997d895fa495fb3421983923219bba93f1a793ee and < c7441c77c91e47f653104be8353b44a3366a5366≥ 028aa21f9e92536038cabb834c15d08f5c894382 and < bcb7164258d0a9a8aa2e73ddccc2d78f67d2519d
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 6.8-rc3version 6.8-rc2version 6.8-rc1≥ 6.7 and < 6.7.6≥ 6.6.4 and < 6.6.18≥ 6.1.65 and < 6.1.79≥ 5.15.141 and < 5.15.152≥ 5.10.203 and < 5.10.213
and 2 more ≥ 5.4.263 and < 5.4.272≥ 4.19.301 and < 4.19.310
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

EPSS over time FIRST

Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 0.24%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux kernel, debian/debian linux
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2024
  • CVE published
    Apr 17, 2024 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

13 on the record

Elsewhere on this site

Debian
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 20h
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 20h
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-26820 is "hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.