Kernel memory exhaustion via failed STB command
Published Dec 30, 2025 · Updated Dec 30, 2025
Memory leak in the AMD PMC STB debugfs handler in Linux 6.3 through 6.3.3 allows local users to consume kernel memory. The amd_pmc_stb_debugfs_open_v2 function allocates buf but returns without freeing it when amd_pmc_send_cmd fails. The STB debug mechanism must be enabled, and debugfs is root-accessible by default; each failed open retains one kernel allocation.
Summary
What happened
Memory leak in the AMD PMC STB debugfs handler in Linux 6.3 through 6.3.3 allows local users to consume kernel memory. The amd_pmc_stb_debugfs_open_v2 function allocates buf but returns without freeing it when amd_pmc_send_cmd fails. The STB debug mechanism must be enabled, and debugfs is root-accessible by default; each failed open retains one kernel allocation.
The record
- CVE
- CVE-2023-54320
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d804adef7b23b22bb82e1b3dd113e9073cea9bc1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f6e7ac4c35a28aef0be93b32c533ae678ad0b9e7
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo