CVE-2026-99433: ocfs2/dlm: hold a lock reference across grant AST enqueue
In the Linux kernel, the following vulnerability has been resolved:
ocfs2/dlm: hold a lock reference across grant AST enqueue
A newly granted remote lock must remain alive until its grant AST is queued. dlmlockmaster() publishes the lock on res->granted with its base and queue references, then drops res->spinlock before calling dlmqueueast(). The resource's reserved AST count does not retain the lock itself.
This can fail when a peer dies with an immediately grantable CREATE buffered on its socket. O2NET's node-down callback flushes receive work before DLM cleanup, but the flush only waits for work queued on entry. A data-ready callback that already selected the socket container can queue new receive work after the flush advances its work color. Socket shutdown does not discard bytes already queued for TCP receive.
The late receive work and DLM node-down cleanup can interleave as follows (the lock reference operations shown are before this fix):
Socket data-ready Node-down thread Receive worker ----------------- ---------------- -------------- o2netdataready() select sc under callback read lock o2netdisconnectnode() queue shutdown begin flush; new color queue scrxwork in the new color release callback lock shutdown socket flush returns read buffered CREATE dlmlockmaster() lock res->spinlock add lock to granted unlock res->spinlock DLM node-down cleanup lock res->spinlock dlmfreedeadlocks() unlink lock put queue/base refs free lock unlock res->spinlock dlmqueueast() dlmqueueast() read lock->lockres (use-after-free)
DLM cleanup holds res->spinlock while dlmfreedeadlocks() drops the queue and base references. The CREATE handler no longer holds that spinlock when dlmqueueast() reads the lock, before taking its AST list reference.
Take a temporary lock reference under res->spinlock when a grant AST will be queued, and drop it after dlmqueueast(). This keeps the lock alive across cleanup until the AST path has taken its own reference, without reversing the existing AST/resource lock order.
KASAN report as below:
BUG: KASAN: slab-use-after-free in dlmqueueast+0x8a4/0xc00 Read of size 8 at addr ffff88810ead5940 by task kworker/u16:3/52
CPU: 3 UID: 0 PID: 52 Comm: kworker/u16:3 Not tainted 7.3.0-rc4-next-20260921-pmb-bt-functional-v1+ #1 PREEMPT(lazy) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, archcaps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: o2net o2netrxuntilempty Call Trace: <TASK> dumpstacklvl+0x93/0xd0 printreport+0xce/0x630 ? dlmqueueast+0x8a4/0xc00 ? srsoaliasreturnthunk+0x5/0xfbef5 ? virtaddrvalid+0x20e/0x420 ? dlmqueueast+0x8a4/0xc00 kasanreport+0xe0/0x110 ? dlmqueueast+0x8a4/0xc00 dlmqueueast+0x8a4/0xc00 ? srsoaliasreturnthunk+0x5/0xfbef5 ? srsoaliasreturnthunk+0x5/0xfbef5 ? dorawspinlock+0x130/0x270 ? pfxdlmqueueast+0x10/0x10 ? pfxdorawspinlock+0x10/0x10 ? rawspinunlockirqrestore+0x45/0x60 ? srs ---truncated---
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2