CVE-2025-21802: net: hns3: fix oops when unload drivers paralleling
In the Linux kernel, the following vulnerability has been resolved:
net: hns3: fix oops when unload drivers paralleling
When unload hclge driver, it tries to disable sriov first for each
ae_dev node from hnae3_ae_dev_list. If user unloads hns3 driver at
the time, because it removes all the ae_dev nodes, and it may cause
oops.
But we can't simply use hnae3_common_lock for this. Because in the
process flow of pci_disable_sriov(), it will trigger the remove flow
of VF, which will also take hnae3_common_lock.
To fixes it, introduce a new mutex to protect the unload process.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21802 is a Linux kernel driver race that can trigger a kernel oops when related hns3/hclge drivers are unloaded at the same time. The business impact is most likely service disruption on affected Linux systems, not confirmed data theft or remote compromise based on the provided sources.
Executive priority
Treat this as a targeted stability risk. Prioritize patching where affected Linux kernels support production networking through hns3/hclge or vendor products cite this CVE. For other systems, handle through normal kernel update governance.
Technical view
The flaw is in the Linux kernel hns3 networking driver unload path. During hclge unload, SR-IOV disablement iterates ae_dev nodes while concurrent hns3 unload may remove those nodes, causing an oops. The kernel fix adds a separate mutex to protect unload processing without deadlocking the existing common lock path.
Likely exposure
Exposure appears limited to affected Linux kernels using the hns3/hclge driver path, especially systems where SR-IOV and driver unload operations are possible. The source bundle does not prove broad default exposure across all Linux hosts.
Exploitation context
The bundle shows no CVSS score, no CWE, and KEV is false. No cited source states active exploitation. The described trigger is a parallel driver unload race, suggesting operational or local-administration conditions rather than a proven remote attack path.
Researcher notes
Evidence supports a race-condition kernel oops fixed upstream by introducing a dedicated unload mutex. The bundle does not establish exploitability beyond the described unload race, nor does it provide CVSS, CWE, proof of active exploitation, or a detailed affected hardware matrix.
Mitigation direction
Apply vendor kernel updates that include the referenced stable kernel fixes.
Check Debian LTS and Siemens advisories if those distributions or products are in use.
Prioritize hosts using affected Linux kernels with hns3/hclge networking drivers.
Avoid parallel hns3/hclge driver unload maintenance workflows until patched.
Track vendor guidance because no standalone workaround is specified in the bundle.
Validation and detection
Inventory Linux kernel versions against the affected and fixed version data in the CVE record.
Confirm whether hns3 or hclge driver modules are present and used.
Verify installed kernels include one of the referenced stable fix commits.
Review Debian LTS and Siemens advisory applicability for managed assets.
Check maintenance procedures for concurrent driver unload operations.
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-2025-21802 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.
0CVSS vectors
3Timeline events
2ADP providers
11Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 20:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.