CVE-2022-50197: cpufreq: zynq: Fix refcount leak in zynq_get_revision
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 179034fb108e3655142f2af0c309cef171c34d68, 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f, 3b01353f1825151a29d08e0868b2bf01e1116ab5.
Low priority for now. Upgrade to Linux Linux 179034fb108e3655142f2af0c309cef171c34d68, 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f, 3b01353f1825151a29d08e0868b2bf01e1116ab5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.16 and later · before 4.14.291
- linux linux kernel4.15 and later · before 4.19.256
- linux linux kernel4.20 and later · before 5.4.211
- linux linux kernel5.5 and later · before 5.10.137
- linux linux kernel5.11 and later · before 5.15.61
- linux linux kernel5.16 and later · before 5.18.18
- linux linux kernel5.19 and later · before 5.19.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.16affected
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before f52c9be1779d70037ae300762d19b08fe3656237affected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before dcbb974254d2a27240c2e50185afdde90f923febaffected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before a530fa52d4fdffc5f010f90c05ac63019b8ff5f8affected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39faffected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before 179034fb108e3655142f2af0c309cef171c34d68affected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before ecefd22d5db7ccb8bec2646e5d25e058fc33162aaffected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before 3b01353f1825151a29d08e0868b2bf01e1116ab5affected · git
- 00f7dc636366f72474b1896f4990b3c086cd2c6d and later · before d1ff2559cef0f6f8d97fba6337b28adb10689e16affected · git
- before 3.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50195Jun 18, 2025 · ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock22Monitor
- ← EarlierCVE-2022-50196Jun 18, 2025 · soc: qcom: ocmem: Fix refcount leak in of_get_ocmem22Monitor
- Later →CVE-2022-50198Jun 18, 2025 · ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 179034fb108e3655142f2af0c309cef171c34d68 | Vendor (CNA) |
| Linux Linux | 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f | Vendor (CNA) |
| Linux Linux | 3b01353f1825151a29d08e0868b2bf01e1116ab5 | Vendor (CNA) |
| Linux Linux | a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 | Vendor (CNA) |
| Linux Linux | d1ff2559cef0f6f8d97fba6337b28adb10689e16 | Vendor (CNA) |
| Linux Linux | dcbb974254d2a27240c2e50185afdde90f923feb | Vendor (CNA) |
| Linux Linux | ecefd22d5db7ccb8bec2646e5d25e058fc33162a | Vendor (CNA) |
| Linux Linux | f52c9be1779d70037ae300762d19b08fe3656237 | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f
- git.kernel.org/stable/c/3b01353f1825151a29d08e0868b2bf01e1116ab5
- git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8
- git.kernel.org/stable/c/d1ff2559cef0f6f8d97fba6337b28adb10689e16
- git.kernel.org/stable/c/dcbb974254d2a27240c2e50185afdde90f923feb
- git.kernel.org/stable/c/ecefd22d5db7ccb8bec2646e5d25e058fc33162a
- git.kernel.org/stable/c/f52c9be1779d70037ae300762d19b08fe3656237
Vendor advisories and official records. Exploit/PoC links are deliberately left out.