CVE-2024-36021: net: hns3: fix kernel crash when devlink reload during pf initialization
In the Linux kernel, the following vulnerability has been resolved:
net: hns3: fix kernel crash when devlink reload during pf 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 taking devl_lock during initialization.
Security readout for executives and security teams
Plain-English summary
CVE-2024-36021 is a Linux kernel hns3 network driver crash issue. During device initialization, a devlink reload can access hardware resources before they are ready, causing a kernel crash. The business impact is likely service disruption on affected Linux systems using this driver, not data theft based on the supplied evidence.
Executive priority
Handle as a targeted reliability risk for Linux systems using hns3 networking. It does not warrant emergency internet-wide response from the supplied evidence, but outages on critical hosts could be material. Prioritize patch verification where affected network hardware is deployed.
Technical view
The hns3 driver registered devlink before hardware initialization completed. If devlink reload ran during PF initialization, it could touch uninitialized hardware resources and crash the kernel. The upstream fix takes devl_lock during initialization to serialize this path.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or vulnerable backports with the hns3 network driver in use. The source lists affected Linux entries including 5.15, 6.1.85, 6.6.26, 6.8.5, and 6.9, but distribution-specific package status is not provided.
Exploitation context
The source bundle does not report active exploitation, public exploit use, CVSS, or KEV listing. The described trigger is a devlink reload during PF initialization, producing a kernel crash. Treat this as a potential local or administrative denial-of-service condition until vendor guidance clarifies attack prerequisites.
Researcher notes
Evidence is narrow and upstream-focused. No CWE, CVSS, exploit status, or distribution package matrix is supplied. The core issue is a race or ordering flaw between devlink reload and hns3 PF hardware initialization, resolved by locking during initialization.
Mitigation direction
Update to a Linux kernel or vendor package containing the referenced stable fixes.
Check your distribution advisory for backported hns3 fixes for CVE-2024-36021.
Avoid devlink reload activity during hns3 PF initialization until patched.
Prioritize remediation on systems where hns3-backed networking supports critical workloads.
Validation and detection
Inventory Linux kernel versions and compare them with vendor CVE-2024-36021 guidance.
Confirm whether the hns3 driver is present or used on affected hosts.
Verify installed kernel packages include one of the referenced stable fixes or vendor backport.
Review crash history for hns3, devlink reload, or PF initialization timing indicators.
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-36021 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.