GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel CephFS client: reclaim during MDS reply handling crashes the kernel via ext4 journal_info

CVE-2026-80528Kernel, userspace & hypervisorcurated

Impact

handle_reply() parks a ceph_mds_request pointer in current->journal_info while populating the inode and dentry cache. An allocation in that window can enter direct reclaim, prune dentries belonging to another filesystem, and dirty an ext4 inode; ext4 then starts a JBD2 transaction, JBD2 reads current->journal_info as a journal handle, and dereferences the Ceph request's r_tid as h_transaction. The record includes the resulting oops in jbd2__journal_start() from the ceph-msgr workqueue. On a GPU node this is an unprivileged-triggerable kernel crash on any host that mounts CephFS alongside an ext4 filesystem and runs under memory pressure - which describes a busy training node with a large page cache - and it takes the whole node and its jobs down.

Who can reach it

Local, no special privilege: any workload doing CephFS metadata activity on a node that also has ext4 mounted, while the node is under enough memory pressure to enter direct reclaim. Not remotely reachable on its own. Nodes without a kernel CephFS mount are unaffected.

What to do

Apply the stable fix, which enters a scoped NOFS allocation context around the region that uses current->journal_info and leaves it after clearing the field. Five stable commits are listed; the record names no fixed release version. Rollout is a patched kernel and a per-node reboot - drain GPU workloads first. There is no configuration mitigation short of not mounting CephFS on the affected hosts.

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.