Local service interruption via Tegra20 node refcount leak
Published Oct 1, 2025 · Updated Oct 1, 2025
Reference-count leak in the Tegra20 clock driver in Linux allows local users to interrupt service through retained kernel resources. During tegra20_clock_init(), of_find_matching_node() increments a device-tree node reference, but the function returns without the required of_node_put(). The affected driver is specific to Tegra20 hardware, and the published record reports availability impact only; no data disclosure or modification is reported.
Summary
What happened
Reference-count leak in the Tegra20 clock driver in Linux allows local users to interrupt service through retained kernel resources. During tegra20_clock_init(), of_find_matching_node() increments a device-tree node reference, but the function returns without the required of_node_put(). The affected driver is specific to Tegra20 hardware, and the published record reports availability impact only; no data disclosure or modification is reported.
The record
- CVE
- CVE-2022-50444
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <0172d14f50098f5736b4b272a1529a3e05419bd6
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <4e343bafe03ff68a62f48f8235cf98f2c685468b
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <53531d00e2a8a28a3bf56ea58b18ff3611824f37
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <5d9fb09612defe7b1d5627db7b3833b46eb21e7b
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <6f76ef65899fcd93ca747ef38d7a41931e61e4fa
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <70f0a0a27d79f689defc5f5f0bd47d07813e6dea
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <8cd228892759d37f36a46616025f4fa0d0a63b5d
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <d6e750535b46e12cdde185b416c415e49e4e6e22
- Affected versionversion=37c26a906527b8a6a252614ca83d21ad318c4e84 <f9bdef9bb60814514a787b84184ecaa269a7c951
- Affected versionversion=3.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo