In the Linux kernel, the following vulnerability has been resolved:
ceph: lock mutex in ceph_mds_check_access()
MDS session OPEN handling replaces mdsc->s_cap_auths under
mdsc->mutex, freeing the previous array and its strings.
ceph_mds_check_access() traverses this array without holding the
mutex. A concurrent session reopen can therefore free the array while
it is being inspected, resulting in a use-after-free like this:
Unable to handle kernel paging request at virtual address 003aaad64b2c8bb9
[...]
Internal error: Oops: 0000000096000004 [#1] SMP
Modules linked in:
CPU: 56 UID: 2953037534 PID: 1253231 Comm: php-cgi8.4 Not tainted 6.18.45-i2-ampere #1146 NONE
[..]
pc : ceph_mds_check_access+0xd4/0x550
lr : ceph_mds_check_access+0xc8/0x550
[...]
Call trace:
ceph_mds_check_access+0xd4/0x550 (P)
ceph_atomic_open+0x138/0xbe8
path_openat+0xa24/0xfa8
do_filp_open+0x94/0x158
do_sys_openat2+0x88/0xf8
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Score: 9.8
AV:N - handle_session() frees mdsc->s_cap_auths on CEPH_SESSION_OPEN delivered over the Ceph messenger TCP session (mds_dispatch, CEPH_MSG_CLIENT_SESSION). CephFS re-exported via nfsd/ksmbd also lets a remote client reach the unlocked walker through ceph_atomic_open.
AC:L - A malicious MDS may send CEPH_SESSION_OPEN even on an already-open session, freeing and replacing s_cap_auths under mdsc->mutex at will. Concurrent open/unlink/setattr, including nfsd/ksmbd on a CephFS export, walk that array without the mutex; the MDS can retry while those operations are in flight.
PR:N - The attacker is the remote MDS peer, or an NFS/SMB client of a CephFS re-export, and needs no Linux UID, capability, or init-namespace root on the victim host, matching other MDS-driven CephFS client CVEs such as CVE-2026-89651.
UI:N - Once CephFS is mounted, as is standard in Rook, Kubernetes, and OpenStack, SESSION_OPEN and VFS/nfsd opens run without any further interactive victim action such as mounting media or opening a user-supplied file at exploit time.
S:U - The use-after-free corrupts kernel heap on the CephFS client host and remains in that kernel's security authority; it is not a VM escape, IOMMU bypass, or sandbox boundary crossing.
C:H - ceph_mds_check_access() and ceph_mds_auth_match() dereference the freed s_cap_auths array and its match.path, gids, and fs_name strings; a use-after-free of those objects enables arbitrary kernel read via heap reuse and is High per kernel UAF guidance.
I:H - The same UAF is heap-sprayable with attacker-controlled SESSION_OPEN allocations (cap_auths_num and string lengths), yielding write and control-flow primitives; kernel guidance scores use-after-free integrity as High.
A:H - The reported oops is a kernel paging fault in ceph_mds_check_access from ceph_atomic_open on the freed array; repeating SESSION_OPEN while the walker runs can oops or panic the client, which is High availability impact.
| Attack Vector |
Network |
Scope |
Unchanged |
| Attack Complexity |
Low |
Confidentiality Impact |
High |
| Privileges Required |
None |
Integrity Impact |
High |
| User Interaction |
None |
Availability Impact |
High |
AV:N - handle_session() frees mdsc->s_cap_auths on CEPH_SESSION_OPEN delivered over the Ceph messenger TCP session (mds_dispatch, CEPH_MSG_CLIENT_SESSION). CephFS re-exported via nfsd/ksmbd also lets a remote client reach the unlocked walker through ceph_atomic_open.
AC:L - A malicious MDS may send CEPH_SESSION_OPEN even on an already-open session, freeing and replacing s_cap_auths under mdsc->mutex at will. Concurrent open/unlink/setattr, including nfsd/ksmbd on a CephFS export, walk that array without the mutex; the MDS can retry while those operations are in flight.
PR:N - The attacker is the remote MDS peer, or an NFS/SMB client of a CephFS re-export, and needs no Linux UID, capability, or init-namespace root on the victim host, matching other MDS-driven CephFS client CVEs such as CVE-2026-89651.
UI:N - Once CephFS is mounted, as is standard in Rook, Kubernetes, and OpenStack, SESSION_OPEN and VFS/nfsd opens run without any further interactive victim action such as mounting media or opening a user-supplied file at exploit time.
S:U - The use-after-free corrupts kernel heap on the CephFS client host and remains in that kernel's security authority; it is not a VM escape, IOMMU bypass, or sandbox boundary crossing.
C:H - ceph_mds_check_access() and ceph_mds_auth_match() dereference the freed s_cap_auths array and its match.path, gids, and fs_name strings; a use-after-free of those objects enables arbitrary kernel read via heap reuse and is High per kernel UAF guidance.
I:H - The same UAF is heap-sprayable with attacker-controlled SESSION_OPEN allocations (cap_auths_num and string lengths), yielding write and control-flow primitives; kernel guidance scores use-after-free integrity as High.
A:H - The reported oops is a kernel paging fault in ceph_mds_check_access from ceph_atomic_open on the freed array; repeating SESSION_OPEN while the walker runs can oops or panic the client, which is High availability impact.
CVSS 3.1