Resource retention via device-node refcount leak
Published Dec 9, 2025 · Updated May 11, 2026
Reference-count leakage in the Linux kernel OMAP SSI probe allows attackers to retain device-node references through failed probe paths. The ssi_probe child-node loop returns or breaks without calling of_node_put(), leaving the current device-tree node referenced. Exposure requires the OMAP SSI driver and a relevant probe path; published sources establish neither an attacker-controlled trigger nor a demonstrated service crash.
Summary
What happened
Reference-count leakage in the Linux kernel OMAP SSI probe allows attackers to retain device-node references through failed probe paths. The ssi_probe child-node loop returns or breaks without calling of_node_put(), leaving the current device-tree node referenced. Exposure requires the OMAP SSI driver and a relevant probe path; published sources establish neither an attacker-controlled trigger nor a demonstrated service crash.
The record
- CVE
- CVE-2022-50641
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=3.16
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <0eff9ef67d91e350d2047c3e13b6c3b7d0c90bf4
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <18e199a5541aad6dc5cf51bc3f712247b2d17894
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <20fbaff6699ea5553c67550e867d6f90b7085447
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <691f23a8475f04c988f7e98066b084e996b40fa0
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <962f22e7f7698f7718d95bd9b63e41fb8cca01a9
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <9a2ea132df860177b33c9fd421b26c4e9a0a9396
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <aa9c0598b10960ad1198044da1e277a89b4e3af6
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <e25f56f8bdf66126a54b5a88bc021c82bfb50b75
- Affected versionversion=b209e047bc743247f74ce79e8827ae1ed556bae0 <e8a218c17d7c5c42d5609ef92d339b47f3d11d02
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
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