LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48820: phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable()

In the Linux kernel, the following vulnerability has been resolved: phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable() This error path needs to decrement "usbphyc->n_pll_cons.counter" before returning.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in STM32 USB PHY clock handling. On a specific error path, the kernel may fail to reduce an internal reference counter. The source bundle does not provide CVSS, impact details, or exploitation evidence, so urgency depends on whether affected STM32-based Linux systems are deployed.

Executive priority

Handle through embedded Linux patch management, with higher priority for internet-facing or safety-critical STM32 devices. There is insufficient evidence to justify emergency response based only on this bundle.

Technical view

CVE-2022-48820 fixes a refcount leak in stm32_usbphyc_pll_enable(). The error path must decrement usbphyc->n_pll_cons.counter before returning. The bundle identifies Linux kernel versions and commit-level references, but does not describe attacker control, privilege requirements, or observable impact.

Likely exposure

Exposure appears limited to Linux systems using the STM32 USBPHYC PHY driver on affected kernel builds. General Linux servers without this STM32 hardware or driver are unlikely to be exposed. Confirm against vendor kernel packages, not only upstream version numbers.

Exploitation context

The provided sources do not indicate active exploitation, public exploit availability, or KEV listing. The available evidence describes a resolved kernel correctness issue, not a demonstrated attack path.

Researcher notes

Key uncertainty is operational impact. Sources only state a missing decrement on an error path in stm32_usbphyc_pll_enable(). Validate reachability in local kernel configuration and hardware context before assigning severity.

Mitigation direction

  • Identify STM32-based Linux devices and their kernel package versions.
  • Check whether vendor kernels include the referenced stable fixes.
  • Prioritize updates through normal kernel or device firmware channels.
  • If no vendor fix is available, monitor vendor guidance for backports.
  • Treat unsupported affected kernels as candidates for upgrade or replacement.

Validation and detection

  • Inventory Linux kernel versions across embedded and STM32-based assets.
  • Confirm whether stm32_usbphyc support is built or loaded on each device.
  • Map deployed kernels to vendor advisories or upstream stable commits.
  • Review release notes for inclusion of the referenced fix commits.
  • Document systems where exposure cannot be confirmed from available evidence.
Prepared
Confidence
medium
Sources
5

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-48820 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
2ADP providers
4Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5b1af71280abd82efbe28cd28d553363dfde0a34, 5b1af71280abd82efbe28cd28d553363dfde0a34, 5b1af71280abd82efbe28cd28d553363dfde0a34unaffected
LinuxLinux5.12, 0, 5.15.24, 5.16.10, 5.17affected
Weakness

CWE details

No CWE listed

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