Linux KernelOperating system · Linux
CVE-2026-52960
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 · uneditedIn the Linux kernel, the following vulnerability has been resolved: ceph: put folios not suitable for writeback The batch holds references to the folios (see `filemap_get_folios`, `folio_batch_release`), so we need to `folio_put` the folios we remove. Tested on v6.18.
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 confidenceIn the Linux kernel's ceph filesystem implementation, when folios are removed from a batch because they are not suitable for writeback, the code fails to properly release the references to those folios. The batch holds references via filemap_get_folios and folio_batch_release, so folio_put must be called on removed folios to avoid reference count leaks.
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
>= 6.15, < 7.0.10= 7.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check kernel versionRun `uname -r` or `cat /proc/version` to get the running kernel versionAffected if The version is >= 6.15 and < 7.0.10, or exactly 7.1
-
Verify Ceph kernel module is loadedRun `lsmod | grep ceph` to check if the ceph kernel module is currently loadedAffected if The ceph module is loaded and the kernel version falls in the affected range
-
Check for active Ceph mount pointsRun `mount | grep ceph` or check `/proc/mounts` for any actively mounted Ceph filesystemsAffected if Any Ceph filesystems are mounted and the kernel version is in the affected range
-
Confirm Ceph writeback activityCheck /sys/kernel/debug/ceph/ for active client sessions or monitor for any ceph-related I/O activity using `cat /proc/$(pgrep -f ceph)/mountinfo 2>/dev/null`Affected if Ceph client is actively performing writeback operations and the kernel version is affected
You are affected if your system runs a Linux kernel between 6.15 and 7.0.10 (exclusive) or exactly version 7.1, and has the Ceph filesystem module loaded or a Ceph filesystem mounted.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.10
Apply the kernel patch to add proper folio_put calls for folios removed from writeback batches in the ceph filesystem module. Update to a kernel version containing the fix.
Linux Kernel 7.0.10 or later (7.2+ recommended as 7.1 is also affected)
- 1. Check the current running kernel version using 'uname -r'
- 2. Verify the version is affected: should be >= 6.15 and < 7.0.10, or exactly 7.1
- 3. Update the package repository for your Linux distribution
- 4. Install kernel version 7.0.10 or later (e.g., 7.0.10, 7.2, or newer stable release) using your distribution's package manager
- 5. Reboot the system to load the new kernel
- 6. Verify the new kernel version is running with 'uname -r' and confirm it is no longer in the affected range
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
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 locallyCheck whether your project pulls in CVE-2026-52960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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