Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability vulnerability in the TPM random-number generator cleanup path. On affected kernels, unregistering a TPM chip can trigger list corruption and a kernel crash. The public record shows a resolved kernel bug, but not confirmed remote exploitation or business-impact details beyond system instability.
Executive priority
Handle through normal kernel patch management unless TPM-related crashes are affecting production. Escalate priority for fleets with AMD fTPM usage, custom kernels, or observed kernel BUG crashes.
Technical view
The flaw is a missing !tpm_amd_is_rng_defective() condition before hwrng_unregister() inside tpm_chip_unregister(). The reported failure is list_del corruption leading to a kernel BUG during modprobe on Linux 6.2.8. The source references stable kernel commits resolving the issue.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with TPM support where the relevant AMD TPM RNG defective-path logic is exercised. The provided affected-version data is incomplete and should be validated against distribution kernel advisories and the referenced stable commits.
Exploitation context
The bundle provides a crash report and kernel fix references, but no KEV listing, public exploit claim, or remote attack path. Treat this as a potential local or operational stability issue unless vendor guidance states otherwise.
Researcher notes
The evidence supports a kernel cleanup-path bug causing list corruption during TPM chip unregister. The source does not provide CVSS, CWE, exploitability analysis, or precise downstream distribution ranges. Avoid asserting active exploitation or broad remote impact.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check Linux distribution advisories for exact fixed package versions.
Prioritize systems using TPM hardware or AMD fTPM paths.
Avoid unsupported custom kernels without the referenced TPM fix.
Validation and detection
Inventory Linux kernel versions across TPM-enabled systems.
Confirm whether deployed kernels include one of the referenced stable commits.
Review kernel logs for TPM or hwrng unregister crashes.
Validate distribution package status against vendor advisories.
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-54073 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.