# CVE-2022-50562: tpm: acpi: Call acpi_put_table() to fix memory leak

> A memory leak in the Linux kernel TPM ACPI driver allows local attackers to cause denial of service by exhausting system memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50562, GHSA-j3g5-wx45-hj5x, UBUNTU-CVE-2022-50562

## What is CVE-2022-50562?

CVE-2022-50562 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

tpm: acpi: Call acpi_put_table() to fix memory leak

The start and length of the event log area are obtained from
TPM2 or TCPA table, so we call acpi_get_table() to get the
ACPI information, but the acpi_get_table() should be coupled with
acpi_put_table() to release the ACPI memory, add the acpi_put_table()
properly to fix the memory leak.

While we are at it, remove the redundant empty line at the
end of the tpm_read_log_acpi().

## Which versions are affected by CVE-2022-50562?


## How do I fix CVE-2022-50562?

Apply the vendor's patch.

## Is CVE-2022-50562 being exploited?

There is no known exploitation of CVE-2022-50562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50562 and fix it if it is affected.

What it is: CVE-2022-50562 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50562 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50562/ (Markdown: https://insights.sbomify.com/CVE-2022-50562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50562
- OSV: https://osv.dev/vulnerability/CVE-2022-50562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50562/
Summaries are generated and may contain mistakes; the official description above is the record.