LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Hyper-V networking flaw where a virtual function network adapter may not be registered correctly after the hv_netvsc driver is unloaded and reloaded. The available sources do not provide CVSS, impact detail, or active exploitation evidence.

Executive priority

Treat this as a targeted kernel maintenance item for Hyper-V Linux workloads, not an emergency internet-facing exposure based on current evidence. Prioritize standard patching where affected systems use accelerated virtual networking.

Technical view

The issue is an ordering bug in hv_netvsc. NET_DEVICE_REGISTER can arrive before netvsc_probe completes because the netdevice notifier is registered early. The kernel fix registers matching visible VFs at the end of netvsc_probe if the earlier event was missed.

Likely exposure

Exposure is most plausible on Linux systems running as Hyper-V guests with hv_netvsc and VF/SR-IOV networking. General Linux systems not using this driver path appear less likely to be exposed.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described condition involves driver unload and reload timing, not a public remote attack path.

Researcher notes

The CVE record’s affected-version data is branch-specific and includes commit identifiers plus stable release ranges. Impact severity is not stated, so validation should focus on applicability of hv_netvsc, VF visibility, and whether the branch-specific fix is present.

Mitigation direction

  • Update affected Linux kernels through the appropriate vendor or distribution channel.
  • Confirm the running kernel includes the relevant stable-branch fix commit.
  • Review Debian LTS and other vendor advisories for packaged kernel status.
  • For Siemens environments, check SSA-265688 for product-specific guidance.
  • If no update is available, follow vendor guidance; no workaround is named in the sources.

Validation and detection

  • Inventory Linux kernel versions on Hyper-V-hosted workloads.
  • Identify systems using hv_netvsc with VF or SR-IOV networking.
  • Map kernel versions to the CVE affected and fixed ranges.
  • Check distribution changelogs for CVE-2024-26820 backports.
  • Document whether the issue is applicable, fixed, or vendor-pending.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26820 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux028aa21f9e92536038cabb834c15d08f5c894382, 997d895fa495fb3421983923219bba93f1a793ee, ff6c130e48a79c826cbc2427bd8b34a7592460cc, 97683466e24c801ee4e865ce90ac7e355db2da59, 5dd83db613be8e5c5d30efed7f42780e9eb18380, 7350c460f7f48a8653a15c5c90fc9070aaa29535, 85520856466ed6bc3b1ccb013cddac70ceb437db, 85520856466ed6bc3b1ccb013cddac70ceb437db, 4.19.301, 5.4.263, 5.10.203, 5.15.141, 6.1.65, 6.6.4unaffected
LinuxLinux6.7, 0, 4.19.310, 5.4.272, 5.10.213, 5.15.152, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.