LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54320: platform/x86/amd: pmc: Fix memory leak in amd_pmc_stb_debugfs_open_v2()

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: pmc: Fix memory leak in amd_pmc_stb_debugfs_open_v2() Function amd_pmc_stb_debugfs_open_v2() may be called when the STB debug mechanism enabled. When amd_pmc_send_cmd() fails, the 'buf' needs to be released.

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 memory leak in the AMD PMC debug path. When a specific AMD PMC command fails while the STB debug mechanism is enabled, allocated memory may not be released. The public record does not provide CVSS, known exploitation, or business-impact details.

Executive priority

Treat this as routine kernel maintenance unless internal evidence shows affected AMD debug functionality is exposed on important systems. There is no sourced evidence of active exploitation or high business impact, but kernel memory leaks should still be addressed through normal patch cycles.

Technical view

The issue is in amd_pmc_stb_debugfs_open_v2() under platform/x86/amd/pmc. If amd_pmc_send_cmd() fails, the allocated buffer is not freed. The source bundle lists Linux kernel 6.3 through 6.4-related versions as affected and references two stable kernel commits resolving the leak.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the AMD PMC driver path and STB debug mechanism enabled. The bundle does not identify affected distributions, cloud images, appliances, or configurations beyond Linux kernel version data.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked KEV. Based on the description, plausible impact is resource exhaustion from a kernel memory leak, but the sources do not establish exploitability, privileges required, or repeatability.

Researcher notes

The public data is sparse: no CVSS, CWE, exploit status, or detailed prerequisite analysis is provided. Research should focus on mapping distro backports, confirming reachable debugfs conditions, and determining whether repeated failed amd_pmc_send_cmd() paths create meaningful denial-of-service risk.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Track Linux distribution advisories for backported CVE-2023-54320 fixes.
  • If patching is delayed, check vendor guidance for AMD PMC STB debug exposure.
  • Prioritize systems where AMD PMC debugfs functionality is enabled.

Validation and detection

  • Inventory Linux kernel versions against the affected 6.3 to 6.4 range.
  • Confirm whether the kernel package includes the referenced stable commits.
  • Check whether AMD PMC and STB debug mechanisms are present or enabled.
  • Review vendor advisories for distro-specific fixed package versions.
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-2023-54320 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
LinuxLinux1ecfd30960d4377c2d85181608936dedd35bb171, 1ecfd30960d4377c2d85181608936dedd35bb171unaffected
LinuxLinux6.3, 0, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

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