Skip to main content
Mallory
HighVulnerability

CVE-2022-50087: Use-after-free in Linux kernel ARM SCPI probe failure handling

Published Jun 18, 2025 · Updated 24 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Linux
IdentifiersCVE-2022-50087CWE-416 · Use After Free

CVE-2022-50087 is a use-after-free vulnerability in the Linux kernel ARM SCPI firmware driver. If driver probing fails after the global scpi_info pointer has been assigned, device-managed memory allocated through devm_kzalloc() is freed while scpi_info retains a reference to it. Subsequent access through get_scpi_ops() can expose the stale pointer and result in use-after-free. The fix keeps scpi_info NULL until probing completes successfully.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Access to freed memory in kernel context can potentially cause a kernel crash or other memory-safety failures, affecting system availability. Arbitrary code execution, privilege escalation, and information disclosure are not established for this specific vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until the kernel can be updated, avoid deployments or operational conditions that cause the ARM SCPI driver probe to fail. No specific interim workaround beyond applying a corrected kernel is available.

Remediation

Patch, then assume compromise.

Install a vendor-supported kernel update containing the ARM SCPI fix that defers assignment of scpi_info until probing succeeds. Fixed Red Hat builds include 4.18.0-553.77.1.el8_10 for RHEL 8, 5.14.0-284.142.1.el9_2 for applicable RHEL 9.2 channels, and 5.14.0-427.94.1.el9_4 for applicable RHEL 9.4 channels. Other release streams and real-time kernels require their corresponding vendor updates. Rocky Linux 8 and CentOS Linux 8.5 deployments should apply the applicable CIQ or TuxCare kernel updates. Reboot into the updated kernel for the fix to take effect.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2022-50087 exploited in the wild?
Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-50087?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2022-50087.
Is there a patch for CVE-2022-50087?
Install a vendor-supported kernel update containing the ARM SCPI fix that defers assignment of scpi_info until probing succeeds. Fixed Red Hat builds include 4.18.0-553.77.1.el8_10 for RHEL 8, 5.14.0-284.142.1.el9_2 for applicable RHEL 9.2 channels, and 5.14.0-427.94.1.el9_4 for applicable RHEL 9.4 channels.
What products are affected by CVE-2022-50087?
Linux Kernel.
How severe is CVE-2022-50087?
CVE-2022-50087 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.21% (11th percentile) as of Oct 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.