LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71147: KEYS: trusted: Fix a memory leak in tpm2_load_cmd

In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: Fix a memory leak in tpm2_load_cmd 'tpm2_load_cmd' allocates a tempoary blob indirectly via 'tpm2_key_decode' but it is not freed in the failure paths. Address this by wrapping the blob into with a cleanup helper.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-71147 is a Linux kernel memory leak in the trusted keys TPM2 load path. The public record says memory allocated during TPM2 key decoding was not freed on failure paths. Business urgency is unclear because no CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Treat this as a kernel maintenance item with uncertain security impact. It should not override known exploited vulnerabilities, but TPM2-dependent Linux fleets should verify patch coverage promptly because kernel memory leaks can become availability or stability concerns.

Technical view

The issue is in tpm2_load_cmd under Linux trusted keys. tpm2_key_decode indirectly allocates a temporary blob, and failure paths did not free it. Kernel stable commits resolve this by wrapping the blob with a cleanup helper. The source bundle does not establish attacker access requirements or reachable impact beyond memory leakage.

Likely exposure

Exposure appears limited to Linux systems with affected kernel versions and relevant trusted keys TPM2 functionality. The affected-version data is incomplete in the bundle, so confirm through distribution advisories or kernel stable commit inclusion.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The bundle does not describe a public exploit, attack vector, privileges required, or whether the leak can cause denial of service.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or detailed reachability analysis. Research should focus on whether unprivileged or containerized users can trigger tpm2_load_cmd failure paths and whether repeated failures produce measurable memory pressure.

Mitigation direction

  • Check Linux vendor or distribution advisories for patched kernel packages.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize systems using TPM2 trusted keys or measured boot workflows.
  • Track vendor severity once CVSS or advisory impact is published.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Identify systems using trusted keys with TPM2 support.
  • Confirm patched packages include one of the referenced stable commits.
  • Review vendor advisory notes for backport status and affected ranges.
Prepared
Confidence
medium
Sources
8

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-2025-71147 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
7Source 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
LinuxLinuxf2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0aunaffected
LinuxLinux5.13, 0, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

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