LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48723: spi: uniphier: fix reference count leak in uniphier_spi_probe()

In the Linux kernel, the following vulnerability has been resolved: spi: uniphier: fix reference count leak in uniphier_spi_probe() The issue happens in several error paths in uniphier_spi_probe(). When either dma_get_slave_caps() or devm_spi_register_master() returns an error code, the function forgets to decrease the refcount of both `dma_rx` and `dma_tx` objects, which may lead to refcount leaks. Fix it by decrementing the reference count of specific objects in those error paths.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver bug in UniPhier SPI initialization error handling. If setup fails at specific points, references to DMA objects may not be released. The public record does not provide a CVSS score, CWE, confirmed exploitation, or broad business impact evidence.

Executive priority

Treat as a low-priority kernel maintenance issue unless your environment uses UniPhier-based platforms. Include it in normal kernel patch cycles and confirm embedded device vendors have shipped fixed builds.

Technical view

In uniphier_spi_probe(), error paths after dma_get_slave_caps() or devm_spi_register_master() can return without decrementing refcounts for dma_rx and dma_tx. The kernel fix adds the missing reference release in those paths. The issue is limited to the UniPhier SPI driver context described in the source.

Likely exposure

Exposure is most likely on Linux systems using kernels with the affected UniPhier SPI driver code, especially UniPhier-based embedded or appliance platforms. General-purpose systems not using this driver are less likely to be exposed.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The described condition occurs during probe failure paths, which suggests operational stability risk rather than a documented remote compromise path.

Researcher notes

Evidence is narrow: the public description identifies two error paths and the leaked dma_rx/dma_tx references. No CVSS vector, CWE, exploit status, or independent impact analysis is included in the provided source bundle.

Mitigation direction

  • Identify Linux kernels containing the affected UniPhier SPI driver code.
  • Update to a vendor kernel that includes the referenced stable fixes.
  • Prioritize UniPhier-based embedded systems and appliances first.
  • Check distribution or hardware vendor advisories for backported fixes.
  • Monitor affected systems for repeated driver probe failures or resource exhaustion.

Validation and detection

  • Inventory kernel versions on systems using UniPhier SPI hardware.
  • Confirm whether the referenced stable commits are present or backported.
  • Review kernel logs for UniPhier SPI probe failures.
  • Verify vendor kernel changelogs mention CVE-2022-48723 or the refcount leak fix.
Prepared
Confidence
medium
Sources
6

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-48723 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
5Source 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
LinuxLinux28d1dddc59f6b7fc085093e7c1e978b33f0caf4c, 28d1dddc59f6b7fc085093e7c1e978b33f0caf4c, 28d1dddc59f6b7fc085093e7c1e978b33f0caf4c, 28d1dddc59f6b7fc085093e7c1e978b33f0caf4cunaffected
LinuxLinux5.6, 0, 5.10.99, 5.15.22, 5.16.8, 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.