LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50389: tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak

In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak In crb_acpi_add(), we get the TPM2 table to retrieve information like start method, and then assign them to the priv data, so the TPM2 table is not used after the init, should be freed, call acpi_put_table() to fix the memory leak.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50389 is a Linux kernel memory leak in TPM initialization. A local user with low privileges could potentially contribute to availability loss, but the sources show no confidentiality or integrity impact and no active exploitation evidence.

Executive priority

Treat this as routine-to-moderate patching. It is not supported as actively exploited, but availability-only kernel flaws still matter on shared infrastructure and systems with strict uptime requirements.

Technical view

In tpm_crb, crb_acpi_add() retrieved the ACPI TPM2 table for start-method data but did not release it after initialization. The kernel fix adds acpi_put_table() to prevent a CWE-401 memory leak. CVSS is 5.5: local attack vector, low privileges, availability impact only.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or unpatched downstream builds containing the TPM CRB ACPI memory leak. Risk is most relevant where TPM2 CRB ACPI support is present. Distro-specific backport status is not provided in the source bundle.

Exploitation context

The CVE record marks KEV as false, and the provided sources do not cite active exploitation or public exploit use. Any practical concern is local availability degradation, not remote compromise, data theft, or privilege escalation based on the cited evidence.

Researcher notes

The source evidence identifies a missing ACPI table release in Linux tpm_crb and lists stable commit references. It does not provide exploit details, distro package mappings, or environmental prerequisites beyond the affected Linux kernel and TPM2 ACPI path.

Mitigation direction

  • Update affected Linux kernels to versions containing the stable tpm_crb fix.
  • Use distribution kernel security updates where available, because fixes may be backported.
  • Check vendor guidance for exact package versions and support status.
  • Prioritize shared or multi-user Linux systems where local users are less trusted.

Validation and detection

  • Inventory Linux kernel versions across affected hosts.
  • Compare running kernels with vendor advisories and the listed stable kernel commits.
  • Confirm downstream changelogs include the tpm_crb acpi_put_table fix.
  • Regression test TPM-dependent boot, attestation, and encryption workflows after patching.
Prepared
Confidence
medium
Sources
10

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50389 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-50389Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941, 30fc8d138e9123f374a3c3867e7c7c5cd4004941unaffected
LinuxLinux4.0, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.17, 6.1.3, 6.2affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.