Kernel resource leak via unreleased device-tree node reference
Published Dec 30, 2025 · Updated Dec 30, 2025
Reference-count leakage in the Tegra114 clock driver in Linux 3.10 through 6.0.2 leaves device-tree node references unreleased. During tegra114_clock_init, of_find_matching_node increments the matching node reference count, but the function omits the corresponding of_node_put after initialization. SUSE assesses local low-privilege availability impact, while public records do not document how an attacker can repeat or otherwise reach the initialization path.
Summary
What happened
Reference-count leakage in the Tegra114 clock driver in Linux 3.10 through 6.0.2 leaves device-tree node references unreleased. During tegra114_clock_init, of_find_matching_node increments the matching node reference count, but the function omits the corresponding of_node_put after initialization. SUSE assesses local low-privilege availability impact, while public records do not document how an attacker can repeat or otherwise reach the initialization path.
The record
- CVE
- CVE-2022-50823
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=2cb5efefd6f7d3e7df9a7430b910a80515821256 <1f0e1cbbaffd729560716e9592aa5e609ea93bb6
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <5984b1d66126b024ee77482602ac6e51b53f4116
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <8cc87a9c142ae0e276a3ff9ce50f78a1668da36f
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <8e1fe30253930c6a67385c19802c5ab8706a76d9
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <a7d3fb5814c73d7d49913e4294f8f508a3038bb4
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <c01bfd23cc13a420b3f6a36bcab98410f49d480d
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <ce699dcdac2bfdb6b238f2517ba41d9623b15f46
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <db16a80c76ea395766913082b1e3f939dde29b2c
- Affected versionversion=2cb5efefd6f7d3e7df9a7430b910a80515821256 <e7a57fb92af52c4da69cd947752e8946e5ada50a
- Affected versionversion=3.10
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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