GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel libceph: use-after-free racing a monmap or osdmap update during CephFS mount

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

Impact

The wait loop in __ceph_open_session() read client->monc.monmap->epoch and client->osdc.osdmap->epoch without holding monc.mutex or osdc.lock, while the receive paths free the old map and install the new one under those locks. A mount that lands while the cluster pushes a fresh monmap or osdmap can dereference a freed map - KASAN reproduces it with generic/395 and generic/397. The practical exposure is a kernel-side use-after-free on nodes that mount CephFS or use RBD via the in-kernel client, which on a GPU fleet is often every compute node that pulls datasets or checkpoints from Ceph. Triggering it needs the race to coincide with a map change, so the realistic outcome is a node crash during cluster churn rather than a controllable attack; the NVD network-reachable score is not supported by the commit message.

Who can reach it

Local - a mount of a Ceph filesystem (or kernel RBD session) that races a monmap/osdmap update. No remote authentication path is described in the record; the trigger is normal mount activity against a cluster undergoing map changes.

What to do

Pick up the stable kernel commits that rewrite the wait loop to take monc.mutex and osdc.lock (and make monmap_show/osdmap_show take them too), then drain and reboot each node onto the patched kernel. No mitigation short of a new kernel; avoiding mounts during cluster map churn only narrows the window.

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.