LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36954: tipc: fix a possible memleak in tipc_buf_append

In the Linux kernel, the following vulnerability has been resolved: tipc: fix a possible memleak in tipc_buf_append __skb_linearize() doesn't free the skb when it fails, so move '*buf = NULL' after __skb_linearize(), so that the skb can be freed on the err path.

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-36954 is a Linux kernel memory leak in the TIPC networking code. The public record says failed buffer linearization could leave memory unreleased. The sources provide fixes in Linux stable branches and Debian LTS updates, but no CVSS score, confirmed exploitation, or detailed business impact.

Executive priority

Treat this as a routine-to-prioritized kernel maintenance item, not an emergency based on current evidence. Accelerate remediation on systems using TIPC or exposed to untrusted network contexts, because kernel memory leaks can affect availability.

Technical view

The bug is in tipc_buf_append. When __skb_linearize() failed, the skb was not freed because *buf could be cleared too early for the error path. Stable fixes move the buffer nulling until after linearization, preserving cleanup on failure.

Likely exposure

Exposure is limited to Linux kernels carrying the vulnerable TIPC code path. Prioritize systems with affected kernel versions and TIPC available, enabled, or operationally used. The bundle lists affected Linux versions and stable commit references, but no CPEs.

Exploitation context

CISA KEV status is false in the bundle, and no cited source claims active exploitation. The public sources describe a kernel memory leak fix, not an exploit chain, prerequisites, or observed attacks.

Researcher notes

The available evidence is sparse: no CVSS, CWE, exploit report, or detailed trigger conditions are included. Analysis should stay anchored to the upstream patch rationale and distribution advisories. Avoid assuming privilege level, reachability, or impact beyond memory leakage.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • For Debian LTS systems, review the cited June 2024 advisories and update affected packages.
  • Prioritize updates on hosts where TIPC is enabled or required.
  • Where TIPC is unnecessary, follow vendor guidance to reduce or disable exposure.
  • Track vendor advisories for distribution-specific fixed kernel package versions.

Validation and detection

  • Inventory Linux kernel versions against the affected versions and stable fix references.
  • Confirm whether TIPC is built, loadable, enabled, or used on each system.
  • Verify installed distribution kernel packages include the relevant backported fix.
  • Review patch management records for Debian LTS updates matching the cited advisories.
  • Monitor kernel logs and memory behavior where TIPC remains enabled.
Prepared
Confidence
medium
Sources
12

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-36954 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
11Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4b1761898861117c97066aea6c58f68a7787f0bf, 64d17ec9f1ded042c4b188d15734f33486ed9966, 6da24cfc83ba4f97ea44fc7ae9999a006101755c, b7df21cf1b79ab7026f545e7bf837bd5750ac026, b7df21cf1b79ab7026f545e7bf837bd5750ac026, b7df21cf1b79ab7026f545e7bf837bd5750ac026, b7df21cf1b79ab7026f545e7bf837bd5750ac026, b7df21cf1b79ab7026f545e7bf837bd5750ac026, b2c8d28c34b3070407cb1741f9ba3f15d0284b8b, 5489f30bb78ff0dafb4229a69632afc2ba20765c, 436d650d374329a591c30339a91fa5078052ed1e, ace300eecbccaa698e2b472843c74a5f33f7dce8unaffected
LinuxLinux5.13, 0, 4.19.314, 5.4.276, 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

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