CVE-2026-99434: ocfs2/heartbeat: unlink live slots when their node is missing
In the Linux kernel, the following vulnerability has been resolved:
ocfs2/heartbeat: unlink live slots when their node is missing
o2hbshutdownslot() returns immediately when its node is no longer in the configfs registry. A slot can still be linked in o2hbliveslots when that lookup fails. Region teardown or startup-error cleanup then frees the slot array without removing its embedded list member.
With the same peer live in another region, the next list update can follow a predecessor into the freed array. Reusing the node number can also make a later insertion encounter that stale member.
Always remove the slot under o2hblivelock, even when node lookup fails. Preserve aggregate membership accounting and the last-region DOWN callback: the existing callback interface explicitly permits a NULL node for DOWN events. Only drop the node reference when lookup returned one. This closes both normal release and startup-abort paths without changing the publication or callback locking protocol.
Also require a configured node before admitting a new live slot in o2hbcheckslot(). The early live-bitmap check is not held through admission: the last live slot in another region can be removed in between. Without a node, admission can then queue an UP event with a NULL argument and hit the event helper's BUGON. Existing live slots can still leave and generate NULL-node DOWN events.
A controlled probe-instrumented test reproduced this while stopping one of two regions after removing the peer from configfs. Its KASAN report includes:
BUG: KASAN: slab-use-after-free in listdelentryvalidorreport+0x1e0/0x210 Read of size 8 at addr ffff888106a4ac60 by task o2hb-pmbd0058b/497 Call Trace: <TASK> dumpstacklvl+0x93/0xd0 printreport+0xce/0x630 kasanreport+0xe0/0x110 listdelentryvalidorreport+0x1e0/0x210 o2hbdodiskheartbeat+0x1591/0x2c50 o2hbthread+0x1ed/0xe70 kthread+0x351/0x460 retfromfork+0x659/0x940 retfromforkasm+0x1a/0x30 </TASK> Allocated by task 491: kasansavestack+0x33/0x60 kasansavetrack+0x14/0x30 kasankmalloc+0xaa/0xb0 kmallocnoprof+0x2de/0x780 o2hbregiondevstore+0x7c2/0x1b60 configfswriteiter+0x2f9/0x4f0 vfswrite+0x639/0x1010 ksyswrite+0x111/0x200 dosyscall64+0x114/0x620 entrySYSCALL64afterhwframe+0x77/0x7f Freed by task 491: kasansavestack+0x33/0x60 kasansavetrack+0x14/0x30 kasansavefreeinfo+0x3b/0x60 kasanslabfree+0x5f/0x80 kfree+0x308/0x580 o2hbunmapslotdata+0x1db/0x330 o2hbregionrelease+0x14b/0x4f0 configitemcleanup+0x14b/0x230 configitemput+0x79/0x90 configfsrmdir+0x58a/0x910 vfsrmdir+0x2e8/0x820 filenamermdir+0x3b1/0x520 x64sysrmdir+0x4b/0x70 dosyscall64+0x114/0x620 entrySYSCALL64afterhwframe+0x77/0x7f
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 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1