nday
CVE-2026-99433

ocfs2/dlm: hold a lock reference across grant AST enqueue

Linux / Linux

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

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.

network
AV:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
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 基本値
8.8 HIGH v3.1

ライフサイクル

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

概要

In the Linux kernel, the following vulnerability has been resolved:

ocfs2/dlm: hold a lock reference across grant AST enqueue

A newly granted remote lock must remain alive until its grant AST is queued. dlmlock_master() publishes the lock on res->granted with its base and queue references, then drops res->spinlock before calling dlm_queue_ast(). The resource's reserved AST count does not retain the lock itself.

This can fail when a peer dies with an immediately grantable CREATE buffered on its socket. O2NET's node-down callback flushes receive work before DLM cleanup, but the flush only waits for work queued on entry. A data-ready callback that already selected the socket container can queue new receive work after the flush advances its work color. Socket shutdown does not discard bytes already queued for TCP receive.

The late receive work and DLM node-down cleanup can interleave as follows (the lock reference operations shown are before this fix):

Socket data-ready        Node-down thread         Receive worker
-----------------        ----------------         --------------
o2net_data_ready()
  select sc under
  callback read lock
                         o2net_disconnect_node()
                           queue shutdown
                           begin flush; new color
  queue sc_rx_work
  in the new color
  release callback lock
                           shutdown socket
                           flush returns
                                                  read buffered CREATE
                                                  dlmlock_master()
                                                    lock res->spinlock
                                                    add lock to granted
                                                    unlock res->spinlock
                         DLM node-down cleanup
                           lock res->spinlock
                           dlm_free_dead_locks()
                             unlink lock
                             put queue/base refs
                             free lock
                           unlock res->spinlock
                                                  dlm_queue_ast()
                                                    __dlm_queue_ast()
                                                    read lock->lockres
                                                    (use-after-free)

DLM cleanup holds res->spinlock while dlm_free_dead_locks() drops the queue and base references. The CREATE handler no longer holds that spinlock when __dlm_queue_ast() reads the lock, before taking its AST list reference.

Take a temporary lock reference under res->spinlock when a grant AST will be queued, and drop it after dlm_queue_ast(). This keeps the lock alive across cleanup until the AST path has taken its own reference, without reversing the existing AST/resource lock order.

KASAN report as below:

BUG: KASAN: slab-use-after-free in __dlm_queue_ast+0x8a4/0xc00
Read of size 8 at addr ffff88810ead5940 by task kworker/u16:3/52

CPU: 3 UID: 0 PID: 52 Comm: kworker/u16:3 Not tainted 7.3.0-rc4-next-20260921-pmb-bt-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: o2net o2net_rx_until_empty
Call Trace:
 <TASK>
 dump_stack_lvl+0x93/0xd0
 print_report+0xce/0x630
 ? __dlm_queue_ast+0x8a4/0xc00
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __virt_addr_valid+0x20e/0x420
 ? __dlm_queue_ast+0x8a4/0xc00
 kasan_report+0xe0/0x110
 ? __dlm_queue_ast+0x8a4/0xc00
 __dlm_queue_ast+0x8a4/0xc00
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_raw_spin_lock+0x130/0x270
 ? __pfx___dlm_queue_ast+0x10/0x10
 ? __pfx_do_raw_spin_lock+0x10/0x10
 ? _raw_spin_unlock_irqrestore+0x45/0x60
 ? srs

---truncated---

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

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

イベント履歴

+DIS公開

Linux が CVE レコードを公開。CVSS 基本値 8.8(重要)。

出典 cvelist · nday が にリアルタイムで観測 · 生データ
{
  "id": 484749,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99433",
  "occurred_at": "2026-11-19T14:41:08.385Z",
  "observed_at": "2026-11-19T15:00:30.436713Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-19T14:41:08.385Z",
    "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.