# clk: tegra: Fix refcount leak in tegra210_clock_init

CVE record · `CVE-2022-50458`

- **Identifiers:** `CVE-2022-50458`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 Oct 2025, 11:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before a19360db83d29bd6b0de4ffad2c815d79246ba99` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before e715510adc20a4a07f157ece4e6d068e648a0383` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before ac010ec3484ba95c6ab3d946f9a83560005c13c6` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before 6d3ac23b952f374017e1a5249d1f03bdbc7f9878` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before f487137a53b1a0692211f7ae82c0a7f87c30bdbe` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before 417ed4432b1b40526b1cb50e535d46900505f6d9` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before 1a6d97139b0a370a9d0809a00e91c41f5bcd3ef1` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before f38f34ba1e1029b927b81b9bf9d952f4ed4007bd` (git)
  - affected: `6b301a059eb2ebed1b12a900e3b21a38e48dd410 to before 56c78cb1f00a9dde8cd762131ce8f4c5eb046fbb` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.5`
  - unaffected: `before 4.5` (semver)
  - unaffected: `4.9.331 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.296 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.262 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.220 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.150 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.75 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.17 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel is affected from version 4.5 until the fix is applied, and stable releases 4.9.331, 4.14.296, 4.19.262, 5.4.220 and later are listed as unaffected. The source gives few details on what an attacker needs or can do; it describes a reference count leak in the Tegra210 clock initialization code. Upgrade to a fixed kernel release. No workaround is listed.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 Oct 2025, 11:45 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50458)
- 1 Oct 2025, 12:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50458)

## Sources

- [CVE List: CVE-2022-50458](https://www.cve.org/CVERecord?id=CVE-2022-50458)
- [NVD: CVE-2022-50458](https://nvd.nist.gov/vuln/detail/CVE-2022-50458)

### References from the CNA

- <https://git.kernel.org/stable/c/a19360db83d29bd6b0de4ffad2c815d79246ba99>
- <https://git.kernel.org/stable/c/e715510adc20a4a07f157ece4e6d068e648a0383>
- <https://git.kernel.org/stable/c/ac010ec3484ba95c6ab3d946f9a83560005c13c6>
- <https://git.kernel.org/stable/c/6d3ac23b952f374017e1a5249d1f03bdbc7f9878>
- <https://git.kernel.org/stable/c/f487137a53b1a0692211f7ae82c0a7f87c30bdbe>
- <https://git.kernel.org/stable/c/417ed4432b1b40526b1cb50e535d46900505f6d9>
- <https://git.kernel.org/stable/c/1a6d97139b0a370a9d0809a00e91c41f5bcd3ef1>
- <https://git.kernel.org/stable/c/f38f34ba1e1029b927b81b9bf9d952f4ed4007bd>
- <https://git.kernel.org/stable/c/56c78cb1f00a9dde8cd762131ce8f4c5eb046fbb>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50458>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50458/>. Everything for agents: <https://agentprime.io/llms.txt>.
