dbcve.org
Linux KernelOperating system · Linux

CVE-2026-43419

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 5.11 / 5.16 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: ceph: fix memory leaks in ceph_mdsc_build_path() Add __putname() calls to error code paths that did not free the "path" pointer obtained by __getname(). If ownership of this pointer is not passed to the caller via path_info.path, the function must free it before returning.

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:>= 5.10.234, < 5.11>= 5.15.177, < 5.16>= 6.1.125, < 6.2>= 6.6, < 6.6.130>= 6.7, < 6.12.78>= 6.13, < 6.18.19>= 6.19, < 6.19.9= 7.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 5.11 / 5.16 / 6.2 or later
Fixed in 5.115.166.2
Vendor patch git.kernel.org →
Recommended fix High confidence

Any stable kernel version >= 6.12 (or >= 6.6.130, >= 6.2, >= 5.16, or >= 5.11 depending on branch)

  1. Identify the currently running Linux kernel version using 'uname -r'
  2. Check if the running kernel version falls within any of the affected ranges: >= 5.10.234 and < 5.11, >= 5.15.177 and < 5.16, >= 6.1.125 and < 6.2, or >= 6.6 and < 6.6.130
  3. If affected, schedule a maintenance window for kernel update
  4. Upgrade to a kernel version >= 5.11, >= 5.16, >= 6.2, or >= 6.6.130 as appropriate for your distribution
  5. For Ubuntu/Debian: 'sudo apt-get update && sudo apt-get upgrade' followed by reboot
  6. For RHEL/CentOS: 'sudo yum update' followed by reboot
  7. For generic source builds, apply vendor patch commit 040d159a45ded7f33201421a81df0aa2a86e5a0b and rebuild kernel
  8. Reboot into the new kernel to apply the fix
Caveat Kernel upgrades may require rebuild of third-party kernel modules; ensure compatibility with existing system components before upgrading

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-2026-43419 — 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-2026-43419 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