CVE-2025-71147
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-02-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.16 (inc) to 6.1.160 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.120 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.64 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.3 (exc) |
| linux | linux_kernel | From 5.13 (inc) to 5.15.198 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's KEYS trusted subsystem. Specifically, the function 'tpm2_load_cmd' allocates a temporary blob indirectly via 'tpm2_key_decode', but this allocated memory is not freed properly in failure paths, leading to a memory leak. The issue was fixed by wrapping the blob with a cleanup helper to ensure proper memory management.
How can this vulnerability impact me? :
The memory leak could lead to increased memory usage and potentially degrade system performance or stability over time if the failure paths are triggered repeatedly. This could affect systems relying on the Linux kernel's TPM2 key handling, possibly causing resource exhaustion.