Service interruption via SPU device-node reference leak
Published Jun 18, 2025 · Updated May 11, 2026
Reference-count leakage in Linux 2.6.20 through 5.19.1 allows local users to interrupt service through the powerpc SPU filesystem. spufs_init_isolated_loader obtains the /spu-isolation device-tree node with of_find_node_by_path but fails to release that reference with of_node_put. The path is limited to PowerPC Cell systems with that device-tree node, and public sources do not disclose how local users repeatedly reach it.
Summary
What happened
Reference-count leakage in Linux 2.6.20 through 5.19.1 allows local users to interrupt service through the powerpc SPU filesystem. spufs_init_isolated_loader obtains the /spu-isolation device-tree node with of_find_node_by_path but fails to release that reference with of_node_put. The path is limited to PowerPC Cell systems with that device-tree node, and public sources do not disclose how local users repeatedly reach it.
The record
- CVE
- CVE-2022-50105
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 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=0afacde3df4c9980f505d9afd7cb0058389732ca <0aa5de2547b7ccf0a31bc740d12f829fae243112
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <14329d29a048dc35aac2374fb3d588d8190095a2
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <4288eb035ba4ddb53245e9365c919bb51ac00c2c
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <43584490ee6c8a104797444af6bf89d0dafe95c0
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <69e9fa07b229badab808980e984a9fe824116f00
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <6ac059dacffa8ab2f7798f20e4bd3333890c541c
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <85aff6a9b7b7ec4e5c319f7946c9864c8d5e3d4a
- Affected versionversion=0afacde3df4c9980f505d9afd7cb0058389732ca <d0cb99948c5f6d8fe56f6e69b8dd0a05ee5f9cec
- Affected versionversion=2.6.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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