CVE-2022-50105: powerpc/spufs: Fix refcount leak in spufs_init_isolated_loader
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.19% (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 0aa5de2547b7ccf0a31bc740d12f829fae243112, 14329d29a048dc35aac2374fb3d588d8190095a2, 4288eb035ba4ddb53245e9365c919bb51ac00c2c.
Low priority for now. Upgrade to Linux Linux 0aa5de2547b7ccf0a31bc740d12f829fae243112, 14329d29a048dc35aac2374fb3d588d8190095a2, 4288eb035ba4ddb53245e9365c919bb51ac00c2c 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: powerpc/spufs: Fix refcount leak in spufs_init_isolated_loader of_find_node_by_path() returns remote device nodepointer 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.1% · 9th 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.1%
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 kernel2.6.20 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
- 2.6.20affected
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 43584490ee6c8a104797444af6bf89d0dafe95c0affected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before d0cb99948c5f6d8fe56f6e69b8dd0a05ee5f9cecaffected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 14329d29a048dc35aac2374fb3d588d8190095a2affected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 85aff6a9b7b7ec4e5c319f7946c9864c8d5e3d4aaffected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 69e9fa07b229badab808980e984a9fe824116f00affected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 0aa5de2547b7ccf0a31bc740d12f829fae243112affected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 4288eb035ba4ddb53245e9365c919bb51ac00c2caffected · git
- 0afacde3df4c9980f505d9afd7cb0058389732ca and later · before 6ac059dacffa8ab2f7798f20e4bd3333890c541caffected · git
- before 2.6.20not 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-50103Jun 18, 2025 · sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed28Monitor
- ← EarlierCVE-2022-50104Jun 18, 2025 · powerpc/xive: Fix refcount leak in xive_get_max_prio22Monitor
- Later →CVE-2022-50106Jun 18, 2025 · powerpc/cell/axon_msi: Fix refcount leak in setup_msi_msg_address22Monitor
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 | 0aa5de2547b7ccf0a31bc740d12f829fae243112 | Vendor (CNA) |
| Linux Linux | 14329d29a048dc35aac2374fb3d588d8190095a2 | Vendor (CNA) |
| Linux Linux | 4288eb035ba4ddb53245e9365c919bb51ac00c2c | Vendor (CNA) |
| Linux Linux | 43584490ee6c8a104797444af6bf89d0dafe95c0 | Vendor (CNA) |
| Linux Linux | 69e9fa07b229badab808980e984a9fe824116f00 | Vendor (CNA) |
| Linux Linux | 6ac059dacffa8ab2f7798f20e4bd3333890c541c | Vendor (CNA) |
| Linux Linux | 85aff6a9b7b7ec4e5c319f7946c9864c8d5e3d4a | Vendor (CNA) |
| Linux Linux | d0cb99948c5f6d8fe56f6e69b8dd0a05ee5f9cec | 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.
No history yet (it accumulates with the daily EPSS job).
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/14329d29a048dc35aac2374fb3d588d8190095a2
- git.kernel.org/stable/c/4288eb035ba4ddb53245e9365c919bb51ac00c2c
- git.kernel.org/stable/c/43584490ee6c8a104797444af6bf89d0dafe95c0
- git.kernel.org/stable/c/69e9fa07b229badab808980e984a9fe824116f00
- git.kernel.org/stable/c/6ac059dacffa8ab2f7798f20e4bd3333890c541c
- git.kernel.org/stable/c/85aff6a9b7b7ec4e5c319f7946c9864c8d5e3d4a
- git.kernel.org/stable/c/d0cb99948c5f6d8fe56f6e69b8dd0a05ee5f9cec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.