GSD-2022-1007653
clk: tegra20: Fix refcount leak in tegra20_clock_init
clk: tegra20: Fix refcount leak in tegra20_clock_init
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v4.9.331 by commit f9bdef9bb60814514a787b84184ecaa269a7c951, it was introduced in version v3.9 by commit 37c26a906527b8a6a252614ca83d21ad318c4e84. For more details please see the references link.
What each source reports
OSV No score
clk: tegra20: Fix refcount leak in tegra20_clock_init
clk: tegra20: Fix refcount leak in tegra20_clock_init
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v4.9.331 by commit f9bdef9bb60814514a787b84184ecaa269a7c951, it was introduced in version v3.9 by commit 37c26a906527b8a6a252614ca83d21ad318c4e84. For more details please see the references link.
- Record
GSD-2022-1007653- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
KernelLinux |
Listed versions, plus commit ranges v3.10v3.10-rc1v3.10-rc2v3.10-rc3v3.10-rc4 Show 45 moreShow lessv3.10-rc5v3.10-rc6v3.10-rc7v3.11v3.11-rc1v3.11-rc2v3.11-rc3v3.11-rc4v3.11-rc5v3.11-rc6v3.11-rc7v3.12v3.12-rc1v3.12-rc2v3.12-rc3v3.12-rc4v3.12-rc5v3.12-rc6v3.12-rc7v3.13v3.13-rc1v3.13-rc2v3.13-rc3v3.13-rc4v3.13-rc5v3.13-rc6v3.13-rc7v3.13-rc8v3.14v3.14-rc1v3.14-rc2v3.14-rc3v3.14-rc4v3.14-rc5v3.14-rc6v3.14-rc7v3.14-rc8v3.15v3.15-rc1v3.15-rc2v3.15-rc3v3.15-rc4v3.15-rc5v3.15-rc6v3.15-rc7 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GSD-2022-1007653 is a vulnerability with no CVSS score yet in Kernel, published November 14, 2022. No source lists public exploit code. No source names a fixed version.
Left out here: 462 versions. The JSON record has them.