LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36967: KEYS: trusted: Fix memory leak in tpm2_key_encode()

In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: Fix memory leak in tpm2_key_encode() 'scratch' is never freed. Fix this by calling kfree() in the success, and in the error case.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-36967 is a Linux kernel memory leak in TPM2 trusted-key handling. The kernel allocated a temporary buffer and did not free it. The public record does not provide CVSS, impact depth, or exploitation evidence, so business urgency depends on affected kernel deployment and use of trusted keys.

Executive priority

Track and patch through normal Linux kernel maintenance unless local exposure is high. Escalate priority for systems relying on TPM2 trusted keys or with strict availability requirements, because memory leaks can contribute to resource exhaustion.

Technical view

The issue is in tpm2_key_encode() under Linux KEYS trusted functionality. The source says the scratch allocation was not freed on success or error paths, and stable commits fix this with kfree(). The bundle lists Linux kernel versions as affected and references multiple stable branch fixes.

Likely exposure

Exposure is most plausible on Linux systems running affected kernel versions and using TPM2-backed trusted keys. The bundle does not identify specific distributions, appliances, cloud images, or configurations beyond Linux kernel version data.

Exploitation context

The bundle does not show active exploitation, public exploit code, KEV listing, or an attack path. Treat this as a kernel resource-management flaw requiring patch verification, not as confirmed active compromise evidence.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. No CVSS, CWE, exploitability assessment, or distribution-specific advisory is present in the bundle. Avoid assuming remote reachability or privilege requirements without vendor analysis.

Mitigation direction

  • Inventory Linux kernel versions across servers, endpoints, appliances, and images.
  • Apply vendor kernel updates containing the referenced stable Linux fixes.
  • Prioritize systems using TPM2 trusted keys or security-sensitive key management.
  • Follow distribution guidance for backported fixes and reboot requirements.
  • Monitor vendor advisories for severity, package names, and release status.

Validation and detection

  • Confirm running kernels are outside affected ranges or include a fixed vendor backport.
  • Check kernel changelogs for CVE-2024-36967 or the trusted keys TPM2 fix.
  • Verify whether TPM2 trusted-key functionality is enabled or operationally used.
  • Confirm patch deployment after reboot by recording active kernel versions.
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-2024-36967 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
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0aunaffected
LinuxLinux5.13, 0, 5.15.160, 6.1.92, 6.6.32, 6.8.11, 6.9.2, 6.10affected
Weakness

CWE details

No CWE listed

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