LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48774: dmaengine: ptdma: Fix the error handling path in pt_core_init()

In the Linux kernel, the following vulnerability has been resolved: dmaengine: ptdma: Fix the error handling path in pt_core_init() In order to free resources correctly in the error handling path of pt_core_init(), 2 goto's have to be switched. Otherwise, some resources will leak and we will try to release things that have not been allocated yet. Also move a dev_err() to a place where it is more meaningful.

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 is a Linux kernel driver cleanup bug. If PTDMA driver initialization fails, the kernel may leak resources and attempt to release resources that were not allocated. The sources do not provide a CVSS score, attacker path, or evidence of exploitation.

Executive priority

Treat this as routine kernel maintenance unless PTDMA is used in production. There is no source-supported evidence of active exploitation, but affected kernels should still be updated through normal patch cycles.

Technical view

The issue is in dmaengine ptdma pt_core_init() error handling. Incorrect goto ordering caused mismatched cleanup on initialization failure. Upstream stable commits correct the cleanup path and move an error log. Affected exposure appears limited to kernels with the PTDMA driver path present and initialized.

Likely exposure

Linux systems running affected 5.15 or 5.16-era kernels with the PTDMA DMA engine driver enabled or loaded. Distribution backports may change exposure, so upstream version checks alone are insufficient.

Exploitation context

CISA KEV status is false in the bundle, and no cited source claims active exploitation. The sources do not describe a remote attack path or practical exploitation conditions.

Researcher notes

The fix is cleanup-path correctness in pt_core_init(), not a clearly documented memory corruption or privilege escalation issue. Validate by mapping vendor kernels to upstream stable commits and confirming whether the PTDMA path can initialize on target hardware.

Mitigation direction

  • Update affected Linux kernels to vendor-supported builds containing the referenced stable fixes.
  • Prioritize systems that enable or load the PTDMA DMA engine driver.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • If immediate patching is unavailable, monitor vendor guidance and PTDMA initialization failures.

Validation and detection

  • Inventory Linux kernel versions against the CVE-listed affected 5.15 and 5.16 entries.
  • Verify whether the running kernel includes a referenced stable commit or distribution backport.
  • Check kernel configuration and loaded modules for PTDMA driver presence.
  • Review boot and kernel logs for PTDMA initialization error messages.
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-48774 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
LinuxLinuxfa5d823b16a9442d609617abeec31da8b6afa224, fa5d823b16a9442d609617abeec31da8b6afa224, fa5d823b16a9442d609617abeec31da8b6afa224unaffected
LinuxLinux5.15, 0, 5.15.25, 5.16.11, 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.