Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-74348— ocfs2/dlm: require a ref for locking_state debugfs open

AI Predicted 5.5 Difficulty: Moderate EPSS 0.18% · P7

Possible ATT&CK Techniques 1AI

T1083 · File and Directory Discovery

Affected Version Matrix 18

VendorProductVersion RangeStatus
LinuxLinux4e3d24ed1a1285fe3289653aacc965642706bacb< 6cc93dea4078cbcddee63fa2234e382a76600464affected
4e3d24ed1a1285fe3289653aacc965642706bacb< 90a6512425414098a63fc97b77bed089c75d106baffected
4e3d24ed1a1285fe3289653aacc965642706bacb< 5bee5d5f67aedd26d2b72e00e49dd93331fbcc30affected
4e3d24ed1a1285fe3289653aacc965642706bacb< aa7883b6a3c76301a3299deb34de948e73bb6a08affected
4e3d24ed1a1285fe3289653aacc965642706bacb< 9c81c1a61a52b6ecf0d14f1dbd95f154a7a9e92aaffected
4e3d24ed1a1285fe3289653aacc965642706bacb< a087b2d3411e7f9df71ba3293596923ee2c70d65affected
4e3d24ed1a1285fe3289653aacc965642706bacb< a09831214912a1f270663d935613910fafd8d883affected
4e3d24ed1a1285fe3289653aacc965642706bacb< 03ad858ce8064861ea580021976dc19b7aabb549affected
… +10 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-74348

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
ocfs2/dlm: require a ref for locking_state debugfs open
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: require a ref for locking_state debugfs open debug_lockres_open() copies inode->i_private into struct debug_lockres and debug_lockres_release() later drops that pointer with dlm_put(). That only works if open successfully pins the struct dlm_ctxt. Today open calls dlm_grab(dlm) but ignores its return value. Once the last domain unregister has removed the context from dlm_domains, dlm_grab() returns NULL, yet open still stores the raw pointer and returns success. The later release path is outside the debugfs removal barrier, so it can call dlm_put() after dlm_free_ctxt_mem() has freed the context. KASAN reports this as a slab-use-after-free in dlm_put() called from debug_lockres_release(). Fail the open when dlm_grab() cannot acquire the reference and unwind the seq_file private state before returning. That keeps locking_state from handing out a file descriptor whose release path does not own the dlm_ctxt. The buggy scenario involves two paths, with each column showing the order within that path: locking_state debugfs open: last domain unregister: 1. debug_lockres_open() reads 1. dlm_unregister_domain() calls inode->i_private. dlm_complete_dlm_shutdown(). 2. debug_lockres_open() calls 2. shutdown removes the dlm_ctxt from dlm_grab(dlm) and gets NULL. dlm_domains. 3. open still stores the raw dlm 3. final teardown reaches pointer in dl->dl_ctxt and dlm_free_ctxt_mem() and frees it. returns success. 4. debug_lockres_release() later calls dlm_put(dl->dl_ctxt). Validation reproduced this kernel report: KASAN slab-use-after-free in dlm_put+0x82/0x200 RIP: 0033:0x7f4d349bc9e0 The buggy address belongs to the object at ffff888103a3c000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 816 bytes inside of freed 2048-byte region [ffff888103a3c000, ffff888103a3c800) Write of size 4 Call trace: dump_stack_lvl+0x66/0xa0 (?:?) print_report+0xd0/0x630 (?:?) dlm_put+0x82/0x200 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x188/0x2f0 (?:?) kasan_report+0xe4/0x120 (?:?) kasan_check_range+0x105/0x1b0 (?:?) debug_lockres_release+0x53/0x80 (fs/ocfs2/dlm/dlmdebug.c:587) dlm_put+0x9/0x200 (?:?) debug_lockres_release+0x5c/0x80 (fs/ocfs2/dlm/dlmdebug.c:587) full_proxy_release+0x67/0x90 (?:?) __fput+0x1df/0x4b0 (?:?) do_raw_spin_lock+0x10f/0x1b0 (?:?) fput_close_sync+0xd2/0x170 (?:?) __x64_sys_close+0x55/0x90 (?:?) do_syscall_64+0x10c/0x640 (arch/x86/entry/syscall_64.c:87) irqentry_exit+0xac/0x6e0 (?:?) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?) Freed by task stack: kasan_save_stack+0x33/0x60 (?:?) kasan_save_track+0x14/0x30 (?:?) kasan_save_free_info+0x3b/0x60 (?:?) __kasan_slab_free+0x5f/0x80 (?:?) kfree+0x30f/0x580 (?:?) dlm_put+0x1ce/0x200 (?:?) dlm_unregister_domain+0xf6/0xb30 (?:?) o2cb_cluster_disconnect+0x6b/0x90 (?:?) ocfs2_cluster_disconnect+0x41/0x70 (?:?) ocfs2_dlm_shutdown+0x1c4/0x220 (?:?) ocfs2_dismount_volume+0x38a/0x550 (?:?) generic_shutdown_super+0xc3/0x220 (?:?) kill_block_super+0x29/0x60 (?:?) deactivate_locked_super+0x66/0xe0 (?:?) cleanup_mnt+0x13d/0x210 (?:?) task_work_run+0xfa/0x170 (?:?) exit_to_user_mode_loop+0xd6/0x430 (?:?) do_syscall_64+0x3cb/0x640 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 4e3d24ed1a1285fe3289653aacc965642706bacb ~ 6cc93dea4078cbcddee63fa2234e382a76600464 -
LinuxLinux 2.6.26 -

II. Public POCs for CVE-2026-74348

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-74348

登录查看更多情报信息。

Patches & Fixes for CVE-2026-74348 (8)

Same Patch Batch · Linux · 2026-08-15 · 848 CVEs total

CVE-2026-72255netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst
CVE-2026-72268fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()
CVE-2026-72267fbdev: carminefb: fix potential memory leak in alloc_carmine_fb()
CVE-2026-72266fbdev: vesafb: fix memory leak in vesafb_probe()
CVE-2026-72265fbdev: nvidia: fix potential memory leak in nvidiafb_probe()
CVE-2026-72264fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
CVE-2026-72262ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get
CVE-2026-72263ASoC: SOF: topology: fix memory leak in snd_sof_load_topology
CVE-2026-72261ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control
CVE-2026-72260ASoC: mediatek: mt8192: Check runtime resume during probe
CVE-2026-72259ASoC: mediatek: mt8192: Release reserved memory on cleanup
CVE-2026-72258ASoC: mediatek: mt8183: Release reserved memory on cleanup
CVE-2026-72256netfilter: xt_cluster: reject template conntracks in hash match
CVE-2026-72257ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback
CVE-2026-72245gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path
CVE-2026-72248netfilter: flowtable: support IPIP tunnel with direct xmit
CVE-2026-72247netfilter: nf_conncount: fix zone comparison in tuple dedup
CVE-2026-72246netfilter: flowtable: use correct direction to set up tunnel route
CVE-2026-72249netfilter: flowtable: use dst in this direction when pushing IPIP header
CVE-2026-72244gpu/buddy: bail out of try_harder when alignment cannot be honoured

Showing top 20 of 848 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-74348

No comments yet


Leave a comment