# clk: tegra20: Fix refcount leak in tegra20_clock_init

CVE record · `CVE-2022-50444`

- **Identifiers:** `CVE-2022-50444`
- **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:42 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: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before f9bdef9bb60814514a787b84184ecaa269a7c951` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 6f76ef65899fcd93ca747ef38d7a41931e61e4fa` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 0172d14f50098f5736b4b272a1529a3e05419bd6` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 5d9fb09612defe7b1d5627db7b3833b46eb21e7b` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 70f0a0a27d79f689defc5f5f0bd47d07813e6dea` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before d6e750535b46e12cdde185b416c415e49e4e6e22` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 8cd228892759d37f36a46616025f4fa0d0a63b5d` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 53531d00e2a8a28a3bf56ea58b18ff3611824f37` (git)
  - affected: `37c26a906527b8a6a252614ca83d21ad318c4e84 to before 4e343bafe03ff68a62f48f8235cf98f2c685468b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.9`
  - unaffected: `before 3.9` (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.

> Linux kernel versions from 3.9 (from commit 37c26a906527b8a6a252614ca83d21ad318c4e84 onward) before the fixed stable releases contain a reference count leak in the Tegra20 clock driver's tegra20_clock_init function. The source describes a missing of_node_put() call after of_find_matching_node(), which leaks a device node reference. The source gives few details on the impact. Upgrade to a fixed stable kernel release, such as 4.9.331, 4.14.296, 4.19.262, 5.4.220 or later in those series.

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:42 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50444)
- 1 Oct 2025, 12:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50444)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/f9bdef9bb60814514a787b84184ecaa269a7c951>
- <https://git.kernel.org/stable/c/6f76ef65899fcd93ca747ef38d7a41931e61e4fa>
- <https://git.kernel.org/stable/c/0172d14f50098f5736b4b272a1529a3e05419bd6>
- <https://git.kernel.org/stable/c/5d9fb09612defe7b1d5627db7b3833b46eb21e7b>
- <https://git.kernel.org/stable/c/70f0a0a27d79f689defc5f5f0bd47d07813e6dea>
- <https://git.kernel.org/stable/c/d6e750535b46e12cdde185b416c415e49e4e6e22>
- <https://git.kernel.org/stable/c/8cd228892759d37f36a46616025f4fa0d0a63b5d>
- <https://git.kernel.org/stable/c/53531d00e2a8a28a3bf56ea58b18ff3611824f37>
- <https://git.kernel.org/stable/c/4e343bafe03ff68a62f48f8235cf98f2c685468b>

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-50444>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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