LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50087: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50087 is a Linux kernel issue in the ARM SCPI firmware driver. If driver probing fails, a global pointer may still reference freed memory, creating a use-after-free condition. The sources do not provide severity, CVSS, exploitability, or active exploitation evidence.

Executive priority

Treat this as a kernel maintenance issue for ARM Linux fleets. Prioritize confirmation and patch planning where ARM SCPI is used, but avoid emergency escalation unless vendor advisories add severity or exploitation evidence.

Technical view

The arm_scpi probe path could leave scpi_info assigned after probe failure. Because get_scpi_ops() exports that value, later callers could use memory allocated by devm_kzalloc() after it was freed. Stable kernel commits ensure scpi_info remains NULL until probe succeeds.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the ARM SCPI firmware driver relevant to their platform. The provided data lists affected Linux kernel versions and stable fix commits, but does not identify distributions, appliances, or runtime configurations.

Exploitation context

No KEV listing is present, and the source bundle provides no cited evidence of active exploitation or public weaponization. The available description supports a kernel use-after-free risk after probe failure, but not a confirmed practical attack path.

Researcher notes

The key evidence is the kernel fix rationale: avoid exporting a stale scpi_info pointer when probe fails. Missing data includes CVSS, CWE, affected distribution mapping, reachable attack surface, and exploit preconditions.

Mitigation direction

  • Check vendor Linux kernel advisories for CVE-2022-50087 guidance.
  • Apply kernel updates containing the relevant stable arm_scpi fix commit.
  • Prioritize ARM platforms where the arm_scpi firmware driver is present.
  • If patching is delayed, follow vendor guidance; no separate mitigation is named.

Validation and detection

  • Inventory systems running the affected Linux kernel versions listed in the CVE record.
  • Determine whether the ARM SCPI firmware driver is built or loaded.
  • Verify deployed kernels include the applicable stable commit from the references.
  • Review kernel vendor changelogs for backported CVE-2022-50087 fixes.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50087 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aa, 8cb7cf56c9fe5412de238465b27ef35b4d2801aaunaffected
LinuxLinux4.4, 0, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.