LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36900: net: hns3: fix kernel crash when devlink reload during initialization

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix kernel crash when devlink reload during initialization The devlink reload process will access the hardware resources, but the register operation is done before the hardware is initialized. So, processing the devlink reload during initialization may lead to kernel crash. This patch fixes this by registering the devlink after hardware initialization.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-36900 is a Linux kernel crash bug in the hns3 network driver. During device startup, a devlink reload can access hardware resources before initialization is complete, potentially crashing the kernel. For affected servers, the business impact is availability risk rather than confirmed data theft or remote compromise.

Executive priority

Schedule remediation through normal kernel patch cycles, with higher priority for production servers using hns3 network hardware. No source indicates active exploitation, but a kernel crash can still cause service interruption.

Technical view

The hns3 driver registered devlink before hardware initialization completed. If devlink reload ran during that window, reload processing could touch uninitialized hardware resources and trigger a kernel crash. The upstream fix delays devlink registration until after hardware initialization.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the hns3 network driver path present and relevant network hardware or configuration. The source bundle does not establish remote reachability, privilege requirements, or broad default exposure.

Exploitation context

The CVE is not marked KEV, and the provided sources do not report active exploitation. The described condition is timing-dependent during initialization and devlink reload. Treat it as a denial-of-service availability issue unless vendor guidance adds stronger exploitability evidence.

Researcher notes

Evidence is narrow: the CVE text describes a race/order-of-initialization crash and the fix approach. No CVSS, CWE, exploit status, privilege model, or remote attack path is provided in the bundle.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Prioritize systems using hns3-supported network adapters or devlink management workflows.
  • Check distribution advisories for exact fixed versions and backport status.
  • Avoid relying on upstream version numbers alone; vendors may backport fixes.

Validation and detection

  • Inventory Linux hosts with affected kernel versions and hns3 driver exposure.
  • Confirm whether the referenced stable commit is present in each deployed kernel build.
  • Review vendor kernel changelogs or advisories for CVE-2024-36900 backports.
  • Check crash logs for hns3, devlink reload, or initialization-time kernel panics.
Prepared
Confidence
medium
Sources
6

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-36900 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
2ADP providers
5Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcd6242991d2e3990c828a7c2215d2d3321f1da39, cd6242991d2e3990c828a7c2215d2d3321f1da39, cd6242991d2e3990c828a7c2215d2d3321f1da39, cd6242991d2e3990c828a7c2215d2d3321f1da39unaffected
LinuxLinux5.15, 0, 6.1.91, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

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