CVE-2022-50039: stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove()
In the Linux kernel, the following vulnerability has been resolved:
stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove()
Commit 09f012e64e4b ("stmmac: intel: Fix clock handling on error and remove
paths") removed this clk_disable_unprepare()
This was partly revert by commit ac322f86b56c ("net: stmmac: Fix clock
handling on remove path") which removed this clk_disable_unprepare()
because:
"
While unloading the dwmac-intel driver, clk_disable_unprepare() is
being called twice in stmmac_dvr_remove() and
intel_eth_pci_remove(). This causes kernel panic on the second call.
"
However later on, commit 5ec55823438e8 ("net: stmmac: add clocks management
for gmac driver") has updated stmmac_dvr_remove() which do not call
clk_disable_unprepare() anymore.
So this call should now be called from intel_eth_pci_remove().
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel cleanup bug in the Intel stmmac Ethernet driver. When the driver is removed, a required clock cleanup call was missing after earlier clock-management changes. The provided sources do not state remote exploitability, business impact, or active abuse.
Executive priority
Treat as a kernel maintenance item unless your fleet depends on the affected Intel stmmac driver path. Prioritize normal patch cycles over emergency response based on current evidence.
Technical view
The issue is in intel_eth_pci_remove(): clk_disable_unprepare() should be called there because stmmac_dvr_remove() no longer performs that cleanup. Earlier fixes removed the call to avoid double-disable panics, but later clock-management changes changed the ownership again.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with the Intel stmmac PCI Ethernet driver path. Source metadata lists affected Linux versions including 5.13, 5.10.138, 5.15.63, 5.19.4, and 6.0, but provides no CPEs.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source reports exploitation. The description concerns a driver remove path, not a network protocol flaw or user-facing API.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, exploit evidence, or detailed impact is provided. Analysis should focus on commit ancestry, downstream backports, and whether the affected cleanup path is reachable in deployed environments.
Mitigation direction
Check Linux vendor advisories for fixed kernel packages.
Prioritize systems using Intel stmmac Ethernet hardware or driver modules.
Apply kernel updates containing the referenced stable fixes.
Avoid ad hoc driver workarounds unless vendor-supported.
Validation and detection
Inventory kernel versions and stmmac Intel driver usage.
Map deployed kernels against vendor fixed-package advisories.
Confirm whether referenced stable commits are present downstream.
Review logs for driver unload or remove-related kernel errors.
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-2022-50039 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
0ADP providers
5Source 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.
Jun 18, 2025, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.