Kernel use-after-free via failed SCPI probe
Published Jun 18, 2025 · Updated Aug 5, 2026
Use-after-free in the ARM SCPI firmware driver in Linux 4.4 and later allows local users to corrupt kernel memory after probe failure. scpi_probe publishes the global scpi_info pointer before initialization completes, so a failed probe frees its devm-managed allocation while get_scpi_ops consumers can still dereference it. Exposure is limited to ARM systems using SCPI, and a probe failure can lead to kernel reads, writes, privilege escalation, or a crash without user interaction.
Summary
What happened
Use-after-free in the ARM SCPI firmware driver in Linux 4.4 and later allows local users to corrupt kernel memory after probe failure. scpi_probe publishes the global scpi_info pointer before initialization completes, so a failed probe frees its devm-managed allocation while get_scpi_ops consumers can still dereference it. Exposure is limited to ARM systems using SCPI, and a probe failure can lead to kernel reads, writes, privilege escalation, or a crash without user interaction.
The record
- CVE
- CVE-2022-50087
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.4
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <08272646cd7c310642c39b7f54348fddd7987643
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <0c29e149b6bb498778ed8a1c9597b51acfba7856
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <18048cba444a7c41dbf42c180d6b46606fc24c51
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <4f2d7b46d6b53c07f44a4f8f8f4438888f0e9e87
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <5aa558232edc30468d1f35108826dd5b3ffe978f
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <689640efc0a2c4e07e6f88affe6d42cd40cc3f85
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <87c4896d5dd7fd9927c814cf3c6289f41de3b562
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.
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