Look up another CVE · open CVE-2026-89652 in the interactive tracker
CVE-2026-89652
ceph: bound copied dentry name length in NFS export get_name
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem fs/ceph. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89652 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way. Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS. Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/ceph/export.c
- What this is
- CEPH DISTRIBUTED FILE SYSTEM CLIENT (CEPH)MAINTAINERS section matched on fs/ceph/ · ceph-devel@vger.kernel.org · Supported
- Kernel module
- ceph
Check it on the machine
grep -w CONFIG_CEPH_FS /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w cephPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sid, bookworm · linux-6.12m
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switch
- CONFIG_CEPH_FS
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-11 (37 days ago)source
- CVSS
- 9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.46%, higher than 38.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- fs/ceph
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 3.15 | 6.6.157 | a294064e0e0f |
| 3.15 | 6.12.109 | 61d9f27b191b |
| 3.15 | 6.18.50 | 06fb5e623cdc |
| 3.15 | 7.2.4 | e7c2fd3893a7 |
| 3.15 | 7.3 | eff8013c5a89 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- ceph_get_name() copies LOOKUPNAME/LSSNAP dentry names from a Ceph MDS reply over TCP, and nfsd reaches that callback via exportfs_decode_fh_raw() when CephFS is re-exported, so a remote MDS (or NFS client against such a gateway) hits the overflow on the network path.
- AC:LAttack complexity, low
- A malicious MDS fully controls dname_len and the name bytes. nfsd lookup of a Ceph directory uses d_obtain_alias() then reconnect_path(), which deterministically calls get_name; no race, rare config, or uncontrollable layout is required.
- PR:NPrivileges required, none
- No local account or capability on the victim is needed. A compromised or malicious MDS supplies the overflowing name, and on NFS-reexported CephFS any remote NFS client can force LOOKUPNAME by presenting a directory filehandle.
- UI:NUser interaction, none
- Once CephFS is mounted and re-exported over NFS, nfsd directory filehandle resolution automatically issues LOOKUPNAME and copies the MDS reply; no extra victim mount, click, or interactive step is required at exploit time.
- S:UScope, unchanged
- The overflow corrupts kernel stack/memory on the NFS/Ceph client host and does not cross a VM, IOMMU, or other security-authority boundary.
- C:HConfidentiality impact, high
- Unbounded memcpy of MDS-controlled name bytes past the NAME_MAX+1 exportfs buffer is memory corruption that can overwrite adjacent kernel objects and be leveraged for arbitrary disclosure.
- I:HIntegrity impact, high
- Attacker-controlled length and contents overflow the NAME_MAX+1 stack buffer in exportfs_decode_fh_raw(), enabling an arbitrary write and control-flow hijacking.
- A:HAvailability impact, high
- The same out-of-bounds write of a 256-byte name buffer by an MDS-chosen length, reported as a KASAN OOB write, reliably oopses or panics the kernel.