GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel libceph: unchecked length from the wire allows out-of-bounds writes in cephx auth

CVSS 9.8CVE-2025-68284Kernel, userspace & hypervisorcurated

Impact

In libceph's cephx handshake, the length field used when decrypting the connection secret and processing service tickets came straight from network packets with no bounds check, so a crafted reply can write past the destination buffer in kernel context. The exposure is to whatever the kernel client talks to during authentication - a Ceph monitor, or anything able to answer in its place on the storage network. Nodes that mount CephFS or map RBD images with the in-kernel client carry this; the result is at minimum a kernel panic that takes the node and every GPU job on it down, with memory corruption the worse case. Clusters using only librbd/libcephfs in userspace are not affected by this code path.

Who can reach it

Whoever can answer the kernel client's cephx handshake: a compromised or impersonated Ceph monitor, or an attacker positioned on the storage network able to respond to the mounting node. No credentials on the node are needed.

What to do

Patched upstream; take the fix from your distribution's stable kernel (commits linked below) and reboot each affected node - kernel client code, so there is no way to reload it under a live mount. Drain and reboot nodes that mount CephFS or map RBD, which on a GPU fleet means draining running jobs. Until then, keep the Ceph monitor and OSD network on an isolated segment unreachable from tenant pods.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.