CVE-2026-99204ModerateLocalRevised 7 Nov

ocfs2/dlm: Protect the recovery list during debugfs reads

MSRC advisory NVD CVE.org

Assessment

Severity: Moderate
CVSS base score: 7.1
Impact: Not stated
Exploitation detected: Unknown: not stated by MSRC
Exploitability: Not assessed
Publicly disclosed: Unknown: not stated by MSRC
EPSS · 30-day forecast: No EPSS score collected
Customer action: Required: follow the MSRC remediation guidance

More details

CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H/E:U
Public detection template: No Nuclei template is listed in the current collected catalog
Component: Mariner
Weakness: —
Issued by: Linux
Published: 29 Oct 2026 · October 2026
Last revised: 7 Nov 2026Information published.

CVSS 3.1 base metricsRed raises the risk · green lowers it

Attack vector: LocalAV:L
Attack complexity: LowAC:L
Privileges required: LowPR:L
User interaction: NoneUI:N
Scope: UnchangedS:U
Confidentiality: HighC:H
Integrity: NoneI:N
Availability: HighA:H

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software

2 affected products

azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
azl3 kernel 6.6.159.1-1 on Azure Linux 3.0

What changed

Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
6 Nov 2026 · 17:32:22 UTC
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
6 Nov 2026 · 16:31:02 UTC
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 17:30:39 UTC
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
2 Nov 2026 · 16:27:39 UTC
Affected products: azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
2 Nov 2026 · 09:04:36 UTC
Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
29 Oct 2026

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version

Field-level log (25)

Up to 100 recent field edits are shown; older edits may be outside retention.

7 Nov 2026 · 08:59:22 UTC Last revised5 Nov 2026 14:48 UTC → 7 Nov 2026 01:50 UTC
6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
6 Nov 2026 · 09:07:49 UTC Last revised1 Nov 2026 14:53 UTC → 5 Nov 2026 14:48 UTC
2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
2 Nov 2026 · 09:04:36 UTC Last revised29 Oct 2026 01:08 UTC → 1 Nov 2026 14:53 UTC
2 Nov 2026 · 09:04:36 UTC Affected productsazl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
29 Oct 2026 · 20:19:26 UTC EPSSNot scored → No EPSS score collected
29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → Unknown: not stated by MSRC
29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → Unknown: not stated by MSRC

Explore global source statements, affected packages and advisory history for CVE-2026-99204. The catalog has a separate collection scope from Microsoft release records.

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2026-99204

Published

ocfs2/dlm: Protect the recovery list during debugfs reads

In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: Protect the recovery list during debugfs reads Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory. Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module. Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged. KASAN report as below: BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0 Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896 CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres 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 ? debug_state_open+0x1169/0x12d0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20e/0x420 ? debug_state_open+0x1169/0x12d0 kasan_report+0xe0/0x110 ? debug_state_open+0x1169/0x12d0 debug_state_open+0x1169/0x12d0 ? __pfx_debug_state_open+0x10/0x10 full_proxy_open_regular+0x193/0x310 do_dentry_open+0x595/0x12d0 ? __pfx_full_proxy_open_regular+0x10/0x10 vfs_open_consume+0xd1/0x400 ? srso_alias_return_thunk+0x5/0xfbef5 path_openat+0x18d0/0x2020 ? __pfx_path_openat+0x10/0x10 do_file_open+0x21e/0x470 ? __pfx_do_file_open+0x10/0x10 ? _raw_spin_unlock+0x23/0x40 ? srso_alias_return_thunk+0x5/0xfbef5 ? alloc_fd+0x3a6/0x6b0 do_sys_openat2+0xf4/0x1b0 ? __pfx_do_sys_openat2+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? __fput+0x5b5/0xa60 __x64_sys_openat+0x136/0x1e0 ? __pfx___x64_sys_openat+0x10/0x10 do_syscall_64+0x114/0x620 entry_SYSCALL_64_after_hwframe+0x77/0x7f [Register dump omitted.] </TASK> Allocated by task 880: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_cache_noprof+0x28d/0x610 dlm_remaster_locks+0x147/0x1d90 dlm_do_recovery+0xde1/0x1580 dlm_recovery_thread+0x109/0x300 kthread+0x351/0x460 ret_from_fork+0x659/0x940 ret_from_fork_asm+0x1a/0x30 Freed by task 880: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 kfree+0x308/0x580 dlm_destroy_recovery_area+0x285/0x460 dlm_remaster_locks+0x17c4/0x1d90 dlm_do_recovery+0xde1/0x1580 dlm_recovery_thread+0x109/0x300 kthread+0x351/0x460 ret_from_fork+0x659/0x940 ret_from_fork_asm+0x1a/0x30 The buggy address belongs to the object at ffff88810662ef80 which belongs to the cache kmalloc-32 of size 32 The buggy address is located 0 bytes inside of freed 32-byte region [ffff88810662ef80, ffff88810662efa0) [Page and memory-state dumps omitted.]

Source published: 28 Oct 2026 10:35:58 UTC
Source modified: 30 Oct 2026 12:42:54 UTC
Observed here: 30 Oct 2026 13:45:33 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.