LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54309: tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation

In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation /dev/vtpmx is made visible before 'workqueue' is initialized, which can lead to a memory corruption in the worst case scenario. Address this by initializing 'workqueue' as the very first step of the driver initialization.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the virtual TPM proxy device. A device node can become visible before required internal setup completes, creating a race that may cause memory corruption. The public record does not provide a CVSS score or confirmed exploitation evidence.

Executive priority

Prioritize normal kernel patch management, with higher urgency for virtualization or multi-tenant Linux hosts exposing vTPM functionality. There is credible memory-corruption impact, but public evidence does not currently show active exploitation or a scored severity.

Technical view

The tpm_vtpm_proxy driver exposes /dev/vtpmx before initializing its workqueue. A racing access during driver initialization can hit uninitialized state and, in the worst case described by the record, cause memory corruption. Stable kernel commits fix this by initializing the workqueue first.

Likely exposure

Exposure is most likely on Linux systems with the tpm_vtpm_proxy driver and /dev/vtpmx available, especially hosts using virtual TPM workflows. Exact risk depends on kernel version, vendor backports, module configuration, and device permissions.

Exploitation context

The source bundle shows no KEV listing, exploit report, public exploit status, or CVSS score. Treat this as a local kernel race condition with incomplete public severity data, not as confirmed active exploitation.

Researcher notes

Key uncertainty is exploitability. The record identifies ordering during driver initialization and a memory-corruption worst case, but does not describe trigger constraints, privileges, or impact beyond that. Research should focus on reachable initialization races and access controls around /dev/vtpmx.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Confirm distribution advisories because kernel fixes may be backported without version changes.
  • Restrict /dev/vtpmx exposure to trusted workloads until patched.
  • Review vTPM usage on virtualization hosts and container platforms.

Validation and detection

  • Check running kernel versions against vendor advisories and fixed stable commits.
  • Determine whether tpm_vtpm_proxy is built, loaded, or available as a module.
  • Verify whether /dev/vtpmx exists and who can access it.
  • Prioritize systems where untrusted users or workloads can reach /dev/vtpmx.
Prepared
Confidence
medium
Sources
10

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-54309 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
9Source 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
LinuxLinux6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4, 6f99612e250041a2402d3b1694bccb149cd424a4unaffected
LinuxLinux4.8, 0, 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

No CWE listed

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