nday
CVE-2026-99692

ocfs2: stop recovery before shutting down local allocators

Linux / Linux

に公開されました。nday はまだ修正の根拠を取得していません。修正がないという意味ではありません。4 つの PoC ソースのいずれにも未掲載です。CISA KEV には現時点で未掲載です。

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
現在の段階
DIS
公開日時
CVSS 基本値
スコアなし

ライフサイクル

横軸は UTC。点=分単位、幅広の帯=日付のみ、白抜き=不明または推定。
日時不明
DIS公開
11-20T05:50Z
PAT修正
記録なし
ANA解析
記録なし
POCPoC
記録なし
ITW悪用
記録なし
KEVKEV
記録なし

概要

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:
 <TASK>
 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
 </TASK>

Allocated by task 538:
 kasan_save_stack+0x33/0x60
 kasan

---truncated---

Original text of the CVE record (cvelist), shown as published.

イベント履歴

+DIS公開

Linux が CVE レコードを公開。

出典 cvelist · nday が にリアルタイムで観測 · 生データ
{
  "id": 494734,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99692",
  "occurred_at": "2026-11-20T05:50:36.544Z",
  "observed_at": "2026-11-20T06:00:12.589971Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-11-20T05:50:36.544Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

研究者の投稿

過去 7 日間に 0 人の研究者が言及

リストの研究者が X でこの CVE に触れた投稿です。原文のまま表示し、nday は検証していません。

リストの研究者が X でこの CVE に触れた投稿は、まだ収集していません。

Discussion

0 comments

No comments yet.