nday
CVE-2026-99691

ocfs2/cluster: unlink socket containers before releasing resources

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in 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
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-20T05:50Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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:
 <TASK>
 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.)

 </TASK>

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---

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

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , observed live · raw
{
  "id": 494733,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99691",
  "occurred_at": "2026-11-20T05:50:35.77Z",
  "observed_at": "2026-11-20T06:00:12.589971Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-11-20T05:50:35.770Z",
    "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.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.