# CVE-2022-50632: drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init()

> A resource leak in the Marvell CN10K TAD PMU driver allows local attackers to cause a denial of service by exhausting kernel resources.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50632, GHSA-4j33-p5x7-pgpc, UBUNTU-CVE-2022-50632

## What is CVE-2022-50632?

CVE-2022-50632 is a denial of service vulnerability in Linux, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init()

tad_pmu_init() won't remove the callback added by cpuhp_setup_state_multi()
when platform_driver_register() failed. Remove the callback by
cpuhp_remove_multi_state() in fail path.

Similar to the handling of arm_ccn_init() in commit 26242b330093 ("bus:
arm-ccn: Prevent hotplug callback leak")

## Which versions are affected by CVE-2022-50632?


## How do I fix CVE-2022-50632?

Apply the vendor's patch.

## Is CVE-2022-50632 being exploited?

There is no known exploitation of CVE-2022-50632 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50632 and fix it if it is affected.

What it is: CVE-2022-50632 is a denial of service vulnerability in Linux, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50632 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50632/ (Markdown: https://insights.sbomify.com/CVE-2022-50632/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50632
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50632
- OSV: https://osv.dev/vulnerability/CVE-2022-50632

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50632/
Summaries are generated and may contain mistakes; the official description above is the record.