PT-2026-152571
CVE-2026-99691
·
Published
2026-11-20
·
Updated
2026-11-20
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/cluster: unlink socket containers before releasing resources
A socket container's node and socket must remain alive while the
container is on sock containers. The debugfs formatter reads sc node
and sc sock under o2net debug lock without taking their references, but
sc kref release() releases both before taking that lock to unlink the
container.
With CONFIG DEBUG FS enabled, a synchronous sender can retain its last
socket-container reference after o2net disconnect node() has detached
the connection and flushed o2net wq. The caller runs outside that
workqueue. After the sender removes its configfs dependency, node
removal can proceed without waiting for the sender's final sc put():
Sender (final sc put) Configfs rmdir Debugfs reader
o2nm undepend item()
Drop node item refs
o2nm node put()
[node can be freed]
sc seq show()
Lock debug lock
Read sc node->nd name
Unlock debug lock
sc node = NULL
o2net debug del sc()
The earlier socket release has a similar window. The container is
still selectable while its socket has been released and sc sock has
not yet been cleared:
Sender (final sc put) Debugfs reader
sock release(sc->sc sock)
[socket can be freed]
sc seq show()
Lock debug lock
Read sc sock->sk fields
Unlock debug lock
sc sock = NULL
...
o2net debug del sc()
Move o2net debug del sc() before releasing either resource. Unlinking
under the existing debug lock waits for an active formatter to finish
and prevents later readers from selecting the container. This covers
both socket fields and node fields, including nd num in the stats
formatter.
KASAN report as below:
BUG: KASAN: slab-use-after-free in string+0x42b/0x470
Read of size 1 at addr ffff88810f56fc90 by task python3/506
CPU: 0 UID: 0 PID: 506 Comm: python3 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
Call Trace:
dump stack lvl+0x93/0xd0
print report+0xce/0x630
kasan report+0xe0/0x110
string+0x42b/0x470
vsnprintf+0x330/0x1110
seq printf+0x1a8/0x260
sc seq show+0x604/0x9f0
seq read iter+0x480/0x1110
seq read+0x362/0x5a0
full proxy read+0x11f/0x180
vfs read+0x1a0/0xc20
ksys read+0x111/0x200
do syscall 64+0x114/0x620
entry SYSCALL 64 after hwframe+0x77/0x7f
(User register dump omitted.)
Allocated by task 497:
kasan save stack+0x33/0x60
kasan save track+0x14/0x30
kasan kmalloc+0xaa/0xb0
kmalloc cache noprof+0x28d/0x610
o2nm node group make item+0xea/0x1a0
configfs mkdir+0x762/0xca0
vfs mkdir+0x399/0x7e0
filename mkdirat+0x129/0x450
x64 sys mkdir+0x70/0xa0
do syscall 64+0x114/0x620
entry SYSCALL 64 after hwframe+0x77/0x7f
Freed by task 505:
kasan save stack+0x33/0x60
kasan save track+0x14/0x30
kasan save free info+0x3b/0x60
kasan slab free+0x5f/0x80
kfree+0x308/0x580
config item cleanup+0x14b/0x230
config item put+0x79/0x90
sc put+0x454/0x6e0
o2net send message vec+0x63d/0x1560
o2net send message+0xa6/0xe0
validation send write+0x17f/0x1d0
full proxy write+0x11f/0x180
vfs write+0x25a/0x1010
ksys write+
---truncated---
Found an issue in the description? Have something to add? Feel free to write us 👾