Back
CVE-2022-50197
cpufreq: zynq: Fix refcount leak in zynq_get_revision
Medium5.5EPSS 0.25%
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: cpufreq: zynq: Fix refcount leak in zynq_get_revision of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.25% · top 84% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < f52c9be1779d70037ae300762d19b08fe3656237
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < dcbb974254d2a27240c2e50185afdde90f923feb
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < a530fa52d4fdffc5f010f90c05ac63019b8ff5f8
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < 179034fb108e3655142f2af0c309cef171c34d68
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < ecefd22d5db7ccb8bec2646e5d25e058fc33162a
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < 3b01353f1825151a29d08e0868b2bf01e1116ab5
- affected 00f7dc636366f72474b1896f4990b3c086cd2c6d – < d1ff2559cef0f6f8d97fba6337b28adb10689e16
- affected 3.16
- unaffected < 3.16
- unaffected 4.14.291 – ≤ 4.14.*
- unaffected 4.19.256 – ≤ 4.19.*
- unaffected 5.4.211 – ≤ 5.4.*
- unaffected 5.10.137 – ≤ 5.10.*
- unaffected 5.15.61 – ≤ 5.15.*
- unaffected 5.18.18 – ≤ 5.18.*
- unaffected 5.19.2 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References (8)
- https://git.kernel.org/stable/c/f52c9be1779d70037ae300762d19b08fe3656237 (opens in a new tab)
- https://git.kernel.org/stable/c/dcbb974254d2a27240c2e50185afdde90f923feb (opens in a new tab)
- https://git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 (opens in a new tab)
- https://git.kernel.org/stable/c/22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f (opens in a new tab)
- https://git.kernel.org/stable/c/179034fb108e3655142f2af0c309cef171c34d68 (opens in a new tab)
- https://git.kernel.org/stable/c/ecefd22d5db7ccb8bec2646e5d25e058fc33162a (opens in a new tab)
- https://git.kernel.org/stable/c/3b01353f1825151a29d08e0868b2bf01e1116ab5 (opens in a new tab)
- https://git.kernel.org/stable/c/d1ff2559cef0f6f8d97fba6337b28adb10689e16 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-50197)Record last updated .