LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53755: dmaengine: ptdma: check for null desc before calling pt_cmd_callback

In the Linux kernel, the following vulnerability has been resolved: dmaengine: ptdma: check for null desc before calling pt_cmd_callback Resolves a panic that can occur on AMD systems, typically during host shutdown, after the PTDMA driver had been exercised. The issue was the pt_issue_pending() function is mistakenly assuming that there will be at least one descriptor in the Submitted queue when the function is called. However, it is possible that both the Submitted and Issued queues could be empty, which could result in pt_cmd_callback() being mistakenly called with a NULL pointer. Ref: Bugzilla Bug 216856.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected AMD systems, most often during host shutdown after the PTDMA driver has been used. The available sources describe a reliability and availability problem, not data theft or remote compromise.

Executive priority

Handle through normal kernel maintenance unless affected AMD systems show shutdown panics or availability impact. There is no cited evidence of active exploitation, but crashes can disrupt operations.

Technical view

The PTDMA driver’s pt_issue_pending() path assumed a descriptor existed in the Submitted queue. When both Submitted and Issued queues were empty, it could call pt_cmd_callback() with a NULL descriptor, causing a kernel panic. Stable kernel commits add the missing NULL check.

Likely exposure

Exposure appears limited to AMD systems running affected Linux kernel versions where the PTDMA driver is present and exercised. Exact distro package exposure needs mapping against vendor kernels and backports.

Exploitation context

The source bundle does not cite active exploitation, public weaponization, or KEV listing. The described trigger is a kernel panic typically observed during host shutdown after PTDMA activity.

Researcher notes

The affected version data is not fully normalized in the source bundle. Treat upstream stable commits as fix anchors, then verify downstream distro backports rather than relying only on version numbers.

Mitigation direction

  • Update to a vendor kernel that includes the referenced stable fixes.
  • Check Linux distribution advisories for backported PTDMA fixes.
  • Prioritize affected AMD hosts with shutdown or reboot reliability issues.
  • If updates are unavailable, follow vendor guidance for operational workarounds.

Validation and detection

  • Inventory AMD hosts and their running kernel versions.
  • Check whether PTDMA-related modules or hardware paths are in use.
  • Review logs for shutdown panics referencing ptdma or pt_cmd_callback.
  • Confirm patched kernels include one of the referenced stable commits.
  • Run shutdown and reboot regression tests after patching representative hosts.
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-2023-53755 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
4Source 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
LinuxLinux6fa7e0e836e23e2c758ac3930b040c8abbbf8a6f, 6fa7e0e836e23e2c758ac3930b040c8abbbf8a6f, 6fa7e0e836e23e2c758ac3930b040c8abbbf8a6funaffected
LinuxLinux5.18, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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