Service interruption via Tegra device-node reference leak
Published Oct 1, 2025 · Updated Oct 1, 2025
A reference-count leak in the Tegra210 clock driver in affected Linux kernels allows local users to exhaust resources and interrupt service. The tegra210_clock_init function retains the node returned by of_find_matching_node because it omits the matching of_node_put release. Reachability is limited to kernels using the NVIDIA Tegra210 clock driver; the documented consequence is availability loss without data disclosure or modification.
Summary
What happened
A reference-count leak in the Tegra210 clock driver in affected Linux kernels allows local users to exhaust resources and interrupt service. The tegra210_clock_init function retains the node returned by of_find_matching_node because it omits the matching of_node_put release. Reachability is limited to kernels using the NVIDIA Tegra210 clock driver; the documented consequence is availability loss without data disclosure or modification.
The record
- CVE
- CVE-2022-50458
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- 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=4.5
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <1a6d97139b0a370a9d0809a00e91c41f5bcd3ef1
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <417ed4432b1b40526b1cb50e535d46900505f6d9
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <56c78cb1f00a9dde8cd762131ce8f4c5eb046fbb
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <6d3ac23b952f374017e1a5249d1f03bdbc7f9878
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <a19360db83d29bd6b0de4ffad2c815d79246ba99
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <ac010ec3484ba95c6ab3d946f9a83560005c13c6
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <e715510adc20a4a07f157ece4e6d068e648a0383
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <f38f34ba1e1029b927b81b9bf9d952f4ed4007bd
- Affected versionversion=6b301a059eb2ebed1b12a900e3b21a38e48dd410 <f487137a53b1a0692211f7ae82c0a7f87c30bdbe
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