Kernel memory leak via unreleased ACPI table
Published Dec 30, 2025 · Updated Dec 30, 2025
Memory leak in the Linux kernel TPM TIS ACPI initialization path from 4.13 leaves ACPI table memory unreleased during device setup. check_acpi_tpm2() obtains the TPM2 ACPI table solely to confirm its presence but omits acpi_put_table(), retaining the table reference after initialization. The published record identifies no repeatable attacker-controlled trigger, so the bounded consequence is a one-time kernel-memory leak when the affected TPM ACPI path runs.
Summary
What happened
Memory leak in the Linux kernel TPM TIS ACPI initialization path from 4.13 leaves ACPI table memory unreleased during device setup. check_acpi_tpm2() obtains the TPM2 ACPI table solely to confirm its presence but omits acpi_put_table(), retaining the table reference after initialization. The published record identifies no repeatable attacker-controlled trigger, so the bounded consequence is a one-time kernel-memory leak when the affected TPM ACPI path runs.
The record
- CVE
- CVE-2022-50824
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
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=4.13
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <3b6c822238da9ee8984803355601bcc603d49cb5
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <43135fb098126ef2cd6ed584900fd7bfa25f95ce
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <8bc6c10d3f389693410adb14b4e9deec01ff6334
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <db9622f762104459ff87ecdf885cc42c18053fd9
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <de667a2704ae799f697fd45cf4317623d8c79fb7
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <e027f3b9fabd2b410a4e6a7651e7a45b87019f23
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <e0d1cf8ef84bb14a673215699fb8acc187aa2c4a
- Affected versionversion=4cb586a188d468e05649575f0689dd2bf8c122e6 <e60fa800a32a693d672b1a091424d780278c4587
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