CVE-2022-50823 addresses a refcount leak in the Linux kernel's Tegra clock driver (tegra114_clock_init). Specifically, the of_find_matching_node() function increments a node pointer's reference count, which was not being decremented with of_node_put() after use, leading to a memory leak. This vulnerability affects the Linux kernel, though specific affected product versions are not detailed. The severity of this vulnerability is considered low, with no assigned CVSS score, indicating a lack of readily exploitable attack vectors or significant immediate impact. The FAUCET Risk Score is 7/100, further suggesting a low-risk scenario. The potential impact is primarily system instability or resource exhaustion over time due to the memory leak, rather than direct compromise. There is no evidence of active exploitation for CVE-2022-50823. No exploit code is available on platforms like Metasploit, Nuclei, or ExploitDB. Community discussion and media coverage are absent, indicating a lack of widespread attention or concern regarding this specific vulnerability.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
| Linux | Linux | 3.10CNA affecteddefault affected | |
| Linux | Linux | >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < 1f0e1cbbaffd729560716e9592aa5e609ea93bb6, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < 5984b1d66126b024ee77482602ac6e51b53f4116, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < 8cc87a9c142ae0e276a3ff9ce50f78a1668da36f, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < 8e1fe30253930c6a67385c19802c5ab8706a76d9, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < a7d3fb5814c73d7d49913e4294f8f508a3038bb4, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < c01bfd23cc13a420b3f6a36bcab98410f49d480d, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < ce699dcdac2bfdb6b238f2517ba41d9623b15f46, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < db16a80c76ea395766913082b1e3f939dde29b2c, >= 2cb5efefd6f7d3e7df9a7430b910a80515821256, < e7a57fb92af52c4da69cd947752e8946e5ada50aCNA affecteddefault unaffected |
CVSS data has not been published for this CVE.
No social media mentions found for this CVE.
No media coverage found for this CVE.