dbcve.org
Linux KernelOperating system · Linux

CVE-2026-52962

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 4.5 / 4.10 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

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 a buffer leak in __ceph_setxattr() The old_blob in __ceph_setxattr() can store ci->i_xattrs.prealloc_blob value during the retry. However, it is never called the ceph_buffer_put() for the old_blob object. This patch fixes the issue of the buffer leak.

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 · high confidence

In the Linux kernel's ceph filesystem module, the __ceph_setxattr() function has a buffer leak where old_blob (which may reference ci->i_xattrs.prealloc_blob during retry operations) is never released via ceph_buffer_put(), causing memory to leak.

MitigationApply the kernel patch that adds the proper ceph_buffer_put() call for old_blob in the retry path of __ceph_setxattr() to release the allocated buffer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.192, < 4.5>= 4.9.192, < 4.10>= 4.14.143, < 4.15>= 4.19.72, < 4.20>= 5.2.14, < 5.3>= 5.3.1, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run `uname -r` or `cat /proc/version` to obtain the running kernel version
    Affected if The kernel version falls within any of these ranges: >= 4.4.192 and < 4.5; OR >= 4.9.192 and < 4.10; OR >= 4.14.143 and < 4.15; OR >= 4.19.72 and < 4.20; OR >= 5.2.14 and < 5.3; OR >= 5.3.1 and < 5.10.258; OR >= 5.11 and < 5.15.209; OR >= 5.16 and < 6.1.175; OR >= 6.2 and < 6.6.141; OR >= 6.7 and <
  2. Verify Ceph kernel module is loaded
    Run `lsmod | grep ceph` or check `/sys/module/ceph` exists to see if the Ceph filesystem module is loaded
    Affected if The Ceph module is loaded or the kernel has Ceph compiled in (indicated by /sys/module/ceph existing)
  3. Check for active Ceph mounts
    Run `mount | grep ceph` or inspect `/proc/mounts` for any Ceph filesystem mounts
    Affected if There are Ceph filesystems currently mounted on the system

You are affected if your system runs an affected kernel version, has the Ceph module loaded or compiled in, and has Ceph filesystems mounted - the memory leak triggers when setting extended attributes (xattr) on Ceph mounts under retry conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Interim mitigation

Apply the kernel patch that adds the proper ceph_buffer_put() call for old_blob in the retry path of __ceph_setxattr() to release the allocated buffer.

Recommended fix High confidence

Upgrade to kernel 4.20 or later (or preferably a modern LTS kernel such as 5.4, 5.10, 5.15, 6.1, or 6.6)

  1. Identify the current kernel version using 'uname -r'
  2. Check which of the affected version ranges (4.4.x, 4.9.x, 4.14.x, 4.19.x) your current kernel falls into
  3. Schedule a maintenance window for the kernel upgrade
  4. Back up critical data before proceeding with the upgrade
  5. Upgrade the Linux kernel to a fixed release: 4.5 or later for 4.4.x branches, 4.10 or later for 4.9.x branches, 4.15 or later for 4.14.x branches, or 4.20 or later for 4.19.x branches
  6. Reboot the system to load the new kernel
  7. Verify the new kernel version is running using 'uname -r'
  8. Confirm the ceph module loads properly and the filesystem is accessible
Caveat Kernel upgrades may require rebuild of third-party kernel modules; verify driver compatibility with the new kernel version

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52962 — 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-52962 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