CVE-2021-47009: KEYS: trusted: Fix memory leak on object td
In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: Fix memory leak on object td
Two error return paths are neglecting to free allocated object td,
causing a memory leak. Fix this by returning via the error return
path that securely kfree's td.
Fixes clang scan-build warning:
security/keys/trusted-keys/trusted_tpm1.c:496:10: warning: Potential
memory leak [unix.Malloc]
Security readout for executives and security teams
Plain-English summary
CVE-2021-47009 is a Linux kernel memory leak in trusted key handling. The public record says two error paths failed to free an allocated object. Evidence does not show active exploitation, CVSS, or business-impact detail, so treat it as a kernel maintenance issue unless affected trusted-key functionality is important in your environment.
Executive priority
Handle through normal kernel patch management. Escalate only if critical systems run affected kernels and use trusted-key functionality, or if a vendor advisory later assigns higher severity or exploitation evidence.
Technical view
The issue is in security/keys/trusted-keys/trusted_tpm1.c, where error returns neglected to free object td. Kernel stable commits changed those paths to use the cleanup route that securely frees td. The source bundle identifies Linux kernel versions and stable commits, but does not provide exploitability analysis or distribution package mappings.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with trusted keys or TPM1 trusted-key code reachable. The provided version data lists Linux 5.10.38, 5.11.22, 5.12, 5.12.5, and 5.13, but exact downstream distro exposure requires vendor mapping.
Exploitation context
The sources describe a memory leak found by clang scan-build and fixed in stable kernel commits. They do not cite public exploitation, KEV listing, exploit maturity, required privileges, or attack path. Do not assume active exploitation from this bundle.
Researcher notes
The record is narrow: a memory leak in trusted_tpm1.c error handling. It does not establish attacker control, reachable call paths, denial-of-service impact, or privilege boundaries. Validation should focus on kernel version, enabled trusted-key configuration, and whether downstream packages include the stable commits.
Mitigation direction
Update affected Linux kernels to vendor builds containing the referenced stable fixes.
Check distribution advisories for package-level mapping to CVE-2021-47009.
Prioritize systems using trusted keys or TPM1 trusted-key functionality.
Use standard kernel patch cadence unless vendor guidance says otherwise.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Compare kernel builds against vendor advisories and the referenced stable commits.
Confirm whether trusted-key and TPM1 trusted-key functionality is enabled or reachable.
Record scanner findings separately from confirmed package exposure.
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-2021-47009 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.