PT-2026-151763

CVE-2026-99552

·

Publicado

2026-11-19

·

Atualizado

2026-11-19

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

In the Linux kernel, the following vulnerability has been resolved:
ocfs2/dlm: drain join handlers before releasing module text
The code for a registered DLM handler must remain resident until its last invocation finishes. dlm unregister net handlers() only removes dlm join handlers from the o2net registry. o2net handler get() takes a kref on the wrapper, but that reference does not pin ocfs2 dlm text. o2net process message() calls nh func after dropping o2net handler lock.
With CONFIG OCFS2 FS O2CB=m, ocfs2 dlm can be loaded independently of ocfs2 stack o2cb while nodemanager continues handling messages from a configured, heartbeating peer. If no dependent module or module reference prevents normal unload, the following ordering is possible:
Receive worker Module unload

o2net handler get() take wrapper kref drop handler lock dlm exit() unregister handlers release DLM module text call saved nh func in released module text
Use o2net unregister and flush handler list() in the shared DLM unregister helper. It first prevents new lookups, then waits for the ordered o2net workqueue to drain, including a concurrent destruction of that queue. The acquired invocation therefore finishes before dlm exit() returns and the loader releases the callback code. The same helper covers partial registration and dlm init() error unwind before module memory is released.
Skip the drain when the private join-handler list is empty. Early dlm init() failures can reach this helper before any handler has been published. Partial-registration failure also reaches it a second time after the first call has already unregistered and drained the list. Neither case needs to take o2net wq mutex or drain unrelated work. The list is changed only by serialized module init/exit paths; a nonempty list still uses the full unregister-and-flush helper.
Oops report as below:
Oops: int3: 0000 [#1] SMP KASAN NOPTI CPU: 2 UID: 0 PID: 54 Comm: kworker/u16:3 Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)
Hardware identification omitted.
Workqueue: o2net o2net rx until empty [ocfs2 nodemanager] RIP: 0010:0xffffffffc0423871 [Instruction byte dump omitted.]
Register dump omitted.
Call Trace: ? o2net rx until empty+0x19b1/0x3300 [ocfs2 nodemanager] ? pfx o2net rx until empty+0x10/0x10 [ocfs2 nodemanager] ? lock acquire+0x190/0x300 ? process one work+0x935/0x1b40 ? process one work+0x834/0x1b40 ? srso alias return thunk+0x5/0xfbef5 ? lock release+0xc8/0x290 ? srso alias return thunk+0x5/0xfbef5 ? process one work+0x9a8/0x1b40 ? pfx process one work+0x10/0x10 ? lock acquire+0x190/0x300 ? lock is held type+0x8f/0x100 ? srso alias return thunk+0x5/0xfbef5 ? worker thread+0x65c/0xe40 ? srso alias return thunk+0x5/0xfbef5 ? kthread parkme+0x177/0x220 ? srso alias return thunk+0x5/0xfbef5 ? pfx worker thread+0x10/0x10 ? kthread+0x351/0x460 ? srso alias return thunk+0x5/0xfbef5 ? pfx kthread+0x10/0x10 ? ret from fork+0x659/0x940 ? pfx ret from fork+0x10/0x10 ? srso alias return thunk+0x5/0xfbef5 ? switch to+0x74f/0xf70 ? pfx kthread+0x10/0x10 ? ret from fork asm+0x1a/0x30 Modules linked in: ocfs2 nodemanager [last unloaded: ocfs2 dlm] ---[ end trace 0000000000000000 ]---
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾