PT-2026-152572
CVE-2026-99692
·
تاريخ النشر
2026-11-20
·
تاريخ التحديث
2026-11-20
الوصف من
الدرجة
N/A
غير متوفرلا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: stop recovery before shutting down local allocators
Recovery completion needs the local allocators until it has finished
reclaiming a failed node's allocation window and truncate log. During
unmount, quota recovery is stopped first, but that leaves recovery state
at OCFS2 REC QUOTA DISABLED. New non-quota recovery can still start.
ocfs2 truncate log shutdown() drains existing completion work and releases
osb tl bh before ocfs2 recovery exit() closes that publication path:
Unmount Recovery
stop quota recovery; disable quotas
truncate log shutdown()
flush existing completion work
recover another failed node
queue completion
flush local log; release buffer
complete truncate log recovery()
use released osb tl bh
recovery exit(): disable and drain
An extra buffer reference alone would still let completion append new
records after the final truncate-log flush.
Split stopping and draining recovery from freeing its state. Stop all
recovery producers and drain completion work before shutting down either
local allocator. Keep recovery-state release at its existing later point,
so its lifetime relative to other teardown users stays unchanged. The
second stop at recovery exit() is harmless once recovery is disabled.
KASAN report as below:
BUG: KASAN: slab-use-after-free in ocfs2 truncate log needs flush+0x23d/0x360
Read of size 8 at addr ffff8881093711e8 by task kworker/u16:3/53
CPU: 0 UID: 0 PID: 53 Comm: kworker/u16:3 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: ocfs2 wq ocfs2 complete recovery
Call Trace:
dump stack lvl+0x93/0xd0
print report+0xce/0x630
? ocfs2 truncate log needs flush+0x23d/0x360
? srso alias return thunk+0x5/0xfbef5
? virt addr valid+0x20e/0x420
? ocfs2 truncate log needs flush+0x23d/0x360
kasan report+0xe0/0x110
? ocfs2 truncate log needs flush+0x23d/0x360
ocfs2 truncate log needs flush+0x23d/0x360
? pfx ocfs2 truncate log needs flush+0x10/0x10
? pfx down write+0x10/0x10
ocfs2 complete truncate log recovery+0x315/0x780
? trace hardirqs on+0x18/0x160
? pfx ocfs2 complete truncate log recovery+0x10/0x10
? ocfs2 complete recovery+0x666/0x11b0
? srso alias return thunk+0x5/0xfbef5
? kfree+0x308/0x580
ocfs2 complete recovery+0x676/0x11b0
? pfx ocfs2 complete recovery+0x10/0x10
? reacquire held locks+0xdd/0x200
? process one work+0x7c8/0x1b40
? srso alias return thunk+0x5/0xfbef5
? lock acquire+0x190/0x300
? pfx autoremove wake function+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
Allocated by task 538:
kasan save stack+0x33/0x60
kasan
---truncated---
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾