CVE-2022-50039

Clock resource leak via omitted teardown call

Published Jun 18, 2025 · Updated May 23, 2026

Resource cleanup flaw in the Intel stmmac driver in Linux allows attackers to leave a device clock enabled via unspecified vectors. The intel_eth_pci_remove() path omits clk_disable_unprepare(), so teardown fails to disable and release the clock prepared for the device. Reachability requires the dwmac-intel PCI removal path to run; the record identifies no attacker-controlled trigger or consequence beyond retained clock state.

CVSS severityUnavailable
Unscored
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource cleanup flaw in the Intel stmmac driver in Linux allows attackers to leave a device clock enabled via unspecified vectors. The intel_eth_pci_remove() path omits clk_disable_unprepare(), so teardown fails to disable and release the clock prepared for the device. Reachability requires the dwmac-intel PCI removal path to run; the record identifies no attacker-controlled trigger or consequence beyond retained clock state.

The record

CVE
CVE-2022-50039
Published
Jun 18, 2025
Updated
May 23, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Jun 18, 2025CVE publishedPublication date reported by the CVE source.
  2. May 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3afe11be6435e126f1507ddf1a9d0e5a0d90b336 <02f3642d8e657c05f382729c165bed46745dc18c
  2. Affected versionversion=5.10.81 <5.10.138
  3. Affected versionversion=5.13
  4. Affected versionversion=5ec55823438e850c91c6b92aec93fb04ebde29e2 <47129531196054b374017555165b47a43cdb6f41
  5. Affected versionversion=5ec55823438e850c91c6b92aec93fb04ebde29e2 <5c23d6b717e4e956376f3852b90f58e262946b50
  6. Affected versionversion=5ec55823438e850c91c6b92aec93fb04ebde29e2 <9400aeb419d35e718e90aa14a97c11229d0a40bc

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=3afe11be6435e126f1507ddf1a9d0e5a0d90b336 <02f3642d8e657c05f382729c165bed46745dc18c; version=5.10.81 <5.10.138; version=5.13; version=5ec55823438e850c91c6b92aec93fb04ebde29e2 <47129531196054b374017555165b47a43cdb6f41; version=5ec55823438e850c91c6b92aec93fb04ebde29e2 <5c23d6b717e4e956376f3852b90f58e262946b50; version=5ec55823438e850c91c6b92aec93fb04ebde29e2 <9400aeb419d35e718e90aa14a97c11229d0a40bc

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo