PT-2026-151762
CVE-2026-99551
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: drain quorum work before removing the cluster
The configured cluster must remain available until an in-flight quorum
decision has finished using its fencing method. o2quo make decision()
drops qs lock before calling o2quo fence self(), which marks heartbeat
regions for unclean stop and then reads
o2nm single cluster->cl fence method. Cluster removal clears the
singleton without waiting for this independent system-workqueue item.
When a failed-quorum decision overlaps removal of the heartbeat regions,
nodes and cluster through configfs, the worker can be preempted after
marking the regions and resume after the singleton has been cleared:
Quorum worker Configfs removal
select fence; drop qs lock
o2hb stop all regions()
remove regions; join heartbeat threads
remove nodes; stop o2net
clear singleton; release cluster
read cl fence method
The resumed read dereferences NULL instead of applying the configured
fencing method. The heartbeat thread's dependency protects the local
node only until the thread exits, and draining o2net does not wait for
qs work.
Add o2quo flush work() to drain pending or running quorum decisions
before clearing the singleton in o2nm cluster group drop item(). By
this point the heartbeat regions and nodes have been removed, so their
work publishers are stopped. The worker can finish while the cluster
and its configured fencing method remain available. It does not acquire
the configfs mutex held by the removal path.
Keep o2quo exit() as the counterpart of o2quo init() for module teardown
and initialization failure, and have it call the same drain helper.
Cluster removal uses only the explicitly named drain operation.
KASAN report as below:
Oops: general protection fault, probably for non-canonical address 0xdffffc000000011b: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x00000000000008d8-0x00000000000008df]
CPU: 0 UID: 0 PID: 72 Comm: kworker/0:2 Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-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: events o2quo make decision
RIP: 0010:o2quo fence self+0x65/0x200
Register dump omitted.
Call Trace:
o2quo make decision+0x345/0x3a0
? pfx o2quo make decision+0x10/0x10
? 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:
---[ end trace 0000000000000000 ]---
Found an issue in the description? Have something to add? Feel free to write us 👾