LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50195: ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock

In the Linux kernel, the following vulnerability has been resolved: ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Replace gcc PXO phandle to pxo_board fixed clock declared in the dts. gcc driver doesn't provide PXO_SRC as it's a fixed-clock. This cause a kernel panic if any driver actually try to use it.

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

Security readout for executives and security teams

Plain-English summary

This CVE describes a Linux kernel device-tree clock definition problem on Qualcomm ARM platforms. If software tries to use the incorrectly referenced PXO clock, the kernel can panic. The business impact is availability loss on affected devices, not confirmed data theft or privilege escalation from the provided sources.

Executive priority

Treat this as targeted availability risk for affected Qualcomm ARM Linux devices. It is not supported by the provided evidence as an internet-wide emergency, but devices in operational or embedded roles should be checked because kernel panics can interrupt service.

Technical view

The issue is in Linux kernel ARM Qualcomm DTS clock references: gcc PXO was used where pxo_board fixed-clock should be referenced. The source says the gcc driver does not provide PXO_SRC, and use by a driver can trigger a kernel panic. Public CVSS, CWE, and exploit details are not provided.

Likely exposure

Exposure appears limited to Linux systems using affected ARM Qualcomm device-tree configurations and drivers that actually request this clock. The provided affected data names Linux kernel versions including 5.14, 5.19.2, and 6.0, but the exact maintained ranges should be verified against vendor kernels.

Exploitation context

The source bundle does not show KEV listing, active exploitation, proof-of-concept exploitation, or remote attack conditions. The described failure mode is a kernel panic when a driver tries to use the missing fixed-clock source, suggesting availability risk under specific hardware and driver conditions.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or detailed affected-product matrix is supplied. Analysis should focus on kernel provenance, board DTS content, downstream patch status, and whether any enabled driver path requests the PXO clock on deployed hardware.

Mitigation direction

  • Review Linux vendor advisories for the exact fixed kernel packages.
  • Prioritize updates for Qualcomm ARM devices using affected kernel trees.
  • Apply vendor-provided kernel updates containing the referenced stable fixes.
  • Track downstream device-vendor kernels that may carry the affected DTS.
  • Avoid inventing local workarounds without vendor validation.

Validation and detection

  • Inventory Linux kernel versions on Qualcomm ARM-based assets.
  • Check device trees for the affected PXO clock reference pattern.
  • Confirm whether downstream kernels include the referenced stable commits.
  • Review kernel logs for clock lookup failures or panic traces.
  • Validate remediation in staging on representative hardware.
Prepared
Confidence
medium
Sources
4

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-50195 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
0ADP providers
3Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40cf5c884a965554a424797afb424ffbca4c24b3, 40cf5c884a965554a424797afb424ffbca4c24b3unaffected
LinuxLinux5.14, 0, 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.