CVE-2022-50820

Callback leak after failed PMU initialization

Published Dec 30, 2025 · Updated Dec 30, 2025

Resource leak in the Linux kernel leaves a CPU hotplug callback registered after ARM DMC-620 PMU initialization fails. In dmc620_pmu_init(), cpuhp_setup_state_multi() installs the callback, but a later platform_driver_register() failure returns without calling cpuhp_remove_multi_state(). The failure path is specific to ARM systems using the DMC-620 PMU driver, and public records do not establish attacker control or a resulting crash.

CVSS severityUnavailable
Unscored
EPSS probability0.23%
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 leak in the Linux kernel leaves a CPU hotplug callback registered after ARM DMC-620 PMU initialization fails. In dmc620_pmu_init(), cpuhp_setup_state_multi() installs the callback, but a later platform_driver_register() failure returns without calling cpuhp_remove_multi_state(). The failure path is specific to ARM systems using the DMC-620 PMU driver, and public records do not establish attacker control or a resulting crash.

The record

CVE
CVE-2022-50820
Published
Dec 30, 2025
Updated
Dec 30, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 30, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 30, 2025Record 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=5.11
  2. Affected versionversion=53c218da220c3619b5befec4674ffa35d590092a <adf7c3bbcc819db6e95b6a61c9822230f0ef4778
  3. Affected versionversion=53c218da220c3619b5befec4674ffa35d590092a <af170afa97e50d4169cfaa7ff4ec5d3841182641
  4. Affected versionversion=53c218da220c3619b5befec4674ffa35d590092a <b99fbe8d949a99fe456f08c7aad421327685aa50
  5. Affected versionversion=53c218da220c3619b5befec4674ffa35d590092a <d9f564c966e63925aac4ba273a9319d7fb6f4b4e

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=5.11; version=53c218da220c3619b5befec4674ffa35d590092a <adf7c3bbcc819db6e95b6a61c9822230f0ef4778; version=53c218da220c3619b5befec4674ffa35d590092a <af170afa97e50d4169cfaa7ff4ec5d3841182641; version=53c218da220c3619b5befec4674ffa35d590092a <b99fbe8d949a99fe456f08c7aad421327685aa50; version=53c218da220c3619b5befec4674ffa35d590092a <d9f564c966e63925aac4ba273a9319d7fb6f4b4e

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)
VectorUnavailable
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