CVE-2022-50444Published Oct 1, 2025 · Oct 1Updated Nov 7
clk: tegra20: Fix refcount leak in tegra20_clock_init
Linux
Medium5.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 37c26a906527b8a6a252614ca83d21ad318c4e84 · < d6e750535b46e12cdde185b416c415e49e4e6e22| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
clk: tegra20: Fix refcount leak in tegra20_clock_init
of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
From the CVE record · Linux
The Linux kernel's tegra20_clock_init function does not release a node reference returned by of_find_matching_node(), causing a reference-count leak. The input does not describe how an attacker could trigger the issue or specify access or user-interaction requirements.
Engineers running Linux kernels with Tegra20 clock support should check their versions; affected versions are not specified.