dbcve.org
Linux KernelOperating system · Linux

CVE-2024-36954

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-30
Fix available
A fix is available. Upgrade to 4.5 / 4.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-401

Allocated memory is never released on some path, so a long-running service or a repeatedly triggered request steadily consumes memory until performance degrades or the process crashes. Attackers exploit it by simply driving the leaking path. Remediation is pairing every allocation with a release and using ownership patterns or tooling to catch what leaks.

General guidance for the memory leak class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.4.271, < 4.5>= 4.9.271, < 4.10>= 4.14.235, < 4.15>= 4.19.193, < 4.19.314>= 5.4.124, < 5.4.276>= 5.10.42, < 5.10.217>= 5.12.9, < 5.15.159>= 5.16, < 6.1.91>= 6.2, < 6.6.31>= 6.7, < 6.8.10= 6.9
Debian LinuxOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.5 / 4.10 / 4.15 or later
Fixed in 4.54.104.15
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 4.5, 4.10, 4.15, or 4.19.314 (depending on which branch you are on)

  1. Identify the currently running kernel version using `uname -r`
  2. Consult your Linux distribution's kernel package manager to check for available updates (e.g., `apt list --upgradable` on Debian/Ubuntu, `yum list kernel` on RHEL/CentOS, or `dnf kernel` on Fedora)
  3. Upgrade the kernel package to version 4.5 or later for 4.4.x kernels, version 4.10 or later for 4.9.x kernels, version 4.15 or later for 4.14.x kernels, or version 4.19.314 or later for 4.19.x kernels
  4. Reboot the system to load the new kernel
  5. Verify the new kernel version is running using `uname -r` and confirm the fix is applied
Caveat Kernel upgrades may require rebuild of out-of-tree modules and could introduce compatibility issues with older drivers or userspace tools; ensure critical modules are available for the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36954 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data