CVE-2022-50039

stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove()

MEDIUM
5.5
CVSS Score
Published: June 18, 2025 at 11:01 AM UTC
Updated: June 17, 2026 at 05:22 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.81 ≤ v < 5.10.1385.13 ≤ v < 5.15.635.13 ≤ v < 5.19.45.13 ≤ v < 6.05.16 ≤ v < 5.19.43afe11be6435e126f1507ddf1a9d0e5a0d90b3365.10.815.135ec55823438e850c91c6b92aec93fb04ebde29e26.0 rc1
Vendor states this is fixed in 02f3642d8e657c05f382729c165bed46745dc18c (fixed)
Vendor states this is fixed in 47129531196054b374017555165b47a43cdb6f41 (fixed)
Vendor states this is fixed in 5c23d6b717e4e956376f3852b90f58e262946b50 (fixed)
Vendor states this is fixed in 9400aeb419d35e718e90aa14a97c11229d0a40bc (fixed)
Vendor states this is fixed in 5.10.138 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.63 (unaffected)
Vendor states this is fixed in 5.19.4 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/02f3642d8e657c05f382729c165bed46745dc18c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/47129531196054b374017555165b47a43cdb6f41
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5c23d6b717e4e956376f3852b90f58e262946b50
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9400aeb419d35e718e90aa14a97c11229d0a40bc

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card