Skip to main content
VulnerabilityPublished

CVE-2026-99433: Linux kernel · ocfs2/dlm: hold a lock reference across grant AST enqueue

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f4ae0b96a4abc7d59088eb2e0a2ee524c15f3bf0 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:49 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f4ae0b96a4abc7d59088eb2e0a2ee524c15f3bf0, 71743471204e21113295c786e5cfa570294234a4, 11643cb726c6077c8d80766516c20ff25ba29609 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to f4ae0b96a4abc7d59088eb2e0a2ee524c15f3bf0, 71743471204e21113295c786e5cfa570294234a4, 11643cb726c6077c8d80766516c20ff25ba29609 or 0eb7cd1641695c5de549516661c9b90ba20f943d.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2c5c54aca9d0263f81bd4886232835ba31f7635a, < f4ae0b96a4abc7d59088eb2e0a2ee524c15f3bf0
Fixed in
  • f4ae0b96a4abc7d59088eb2e0a2ee524c15f3bf0
LinuxLinuxAffected
  • ≥ 2c5c54aca9d0263f81bd4886232835ba31f7635a, < 71743471204e21113295c786e5cfa570294234a4
Fixed in
  • 71743471204e21113295c786e5cfa570294234a4
LinuxLinuxAffected
  • ≥ 2c5c54aca9d0263f81bd4886232835ba31f7635a, < 11643cb726c6077c8d80766516c20ff25ba29609
Fixed in
  • 11643cb726c6077c8d80766516c20ff25ba29609
LinuxLinuxAffected
  • ≥ 2c5c54aca9d0263f81bd4886232835ba31f7635a, < 0eb7cd1641695c5de549516661c9b90ba20f943d
Fixed in
  • 0eb7cd1641695c5de549516661c9b90ba20f943d
LinuxLinuxAffected
  • =2.6.25
Fixed in–

Description

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. dlmlock_master() publishes the lock on res->granted with its base and queue references, then drops res->spinlock before calling dlm_queue_ast(). 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 ----------------- ---------------- -------------- o2net_data_ready() select sc under callback read lock o2net_disconnect_node() queue shutdown begin flush; new color queue sc_rx_work in the new color release callback lock shutdown socket flush returns read buffered CREATE dlmlock_master() lock res->spinlock add lock to granted unlock res->spinlock DLM node-down cleanup lock res->spinlock dlm_free_dead_locks() unlink lock put queue/base refs free lock unlock res->spinlock dlm_queue_ast() __dlm_queue_ast() read lock->lockres (use-after-free) DLM cleanup holds res->spinlock while dlm_free_dead_locks() drops the queue and base references. The CREATE handler no longer holds that spinlock when __dlm_queue_ast() 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 dlm_queue_ast(). 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 __dlm_queue_ast+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, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: o2net o2net_rx_until_empty Call Trace: <TASK> dump_stack_lvl+0x93/0xd0 print_report+0xce/0x630 ? __dlm_queue_ast+0x8a4/0xc00 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20e/0x420 ? __dlm_queue_ast+0x8a4/0xc00 kasan_report+0xe0/0x110 ? __dlm_queue_ast+0x8a4/0xc00 __dlm_queue_ast+0x8a4/0xc00 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_raw_spin_lock+0x130/0x270 ? __pfx___dlm_queue_ast+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x45/0x60 ? srs ---truncated---

References

Community reviews

Loading reviews…