{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74351 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74351 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74351 and fix it if it is affected.\n\nWhat it is: CVE-2026-74351 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74351 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74351/ (Markdown: https://insights.sbomify.com/CVE-2026-74351/index.md)","id":"CVE-2026-74351","markdown":"https://insights.sbomify.com/CVE-2026-74351/index.md","name":"CVE-2026-74351","record":{"aliases":["BELL-CVE-2026-74351","DEBIAN-CVE-2026-74351","GHSA-277m-9mg9-wh9q","UBUNTU-CVE-2026-74351"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel OCFS2 filesystem allows local attackers to cause a denial of service or potentially execute code via debugfs.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: rebase copied fsdlm LVB pointers in locking_state\n\nThe locking_state debugfs iterator snapshots struct ocfs2_lock_res by\nvalue under ocfs2_dlm_tracking_lock and later formats that copy in\nocfs2_dlm_seq_show().  That is fine for the inline fields, but the\nuserspace fsdlm stack stores the LVB through lksb_fsdlm.sb_lvbptr.  Once\nthe iterator drops the tracking lock, a copied non-NULL sb_lvbptr still\npoints into the original lockres owner, so teardown can free that\ncontainer before the debugfs dump walks the raw LVB bytes.\n\nRebase the copied sb_lvbptr to the copied l_lksb before dumping the raw\nLVB.  The seq snapshot already carries the inline LVB storage reserved in\nstruct ocfs2_dlm_lksb, so the debugfs reader can dump the copied bytes\nwithout borrowing the original lockres lifetime.\n\nThe buggy scenario involves two paths, with each column showing the order\nwithin that path:\n\nlocking_state reader:                  lockres teardown:\n1. ocfs2_dlm_seq_start()/next()        1. file release or another owner\n   copies struct ocfs2_lock_res           teardown reaches\n2. ocfs2_dlm_seq_show() formats           ocfs2_lock_res_free()\n   the copied row                      2. the lockres is removed from the\n3. ocfs2_dlm_lvb() follows the            tracking list\n   copied sb_lvbptr                   3. the owner frees the original\n                                          lockres container\n\nValidation reproduced this kernel report:\nKASAN slab-use-after-free in ocfs2_dlm_seq_show+0x1bd/0x430\nRIP: 0033:0x7f8ec4b1e29d\nThe buggy address belongs to the object at ffff88810a1e0800 which belongs\nto the cache kmalloc-1k of size 1024\nThe buggy address is located 368 bytes inside of freed 1024-byte region\n[ffff88810a1e0800, ffff88810a1e0c00)\nRead of size 1\nCall trace:\n  dump_stack_lvl+0x66/0xa0\n  print_report+0xce/0x630\n  ocfs2_dlm_seq_show+0x1bd/0x430 (fs/ocfs2/dlmglue.c:3137)\n  srso_alias_return_thunk+0x5/0xfbef5\n  __virt_addr_valid+0x19f/0x330\n  kasan_report+0xe0/0x110\n  seq_read_iter+0x29d/0x790\n  seq_read+0x20a/0x280\n  find_held_lock+0x2b/0x80\n  rcu_read_unlock+0x18/0x70\n  full_proxy_read+0x9e/0xd0\n  vfs_read+0x12c/0x590\n  ksys_read+0xd2/0x170\n  do_user_addr_fault+0x65a/0x890\n  do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87)\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f\nAllocated by task stack:\n  kasan_save_stack+0x33/0x60\n  kasan_save_track+0x14/0x30\n  __kasan_kmalloc+0xaa/0xb0\n  ocfs2_file_open+0x13e/0x300\n  do_dentry_open+0x233/0x7f0\n  vfs_open+0x5a/0x1b0\n  path_openat+0x66d/0x1540\n  do_file_open+0x186/0x2b0\n  do_sys_openat2+0xce/0x150\n  __x64_sys_openat+0xd0/0x140\n  do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87)\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f\nFreed by task stack:\n  kasan_save_stack+0x33/0x60\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x5f/0x80\n  kfree+0x313/0x590\n  ocfs2_file_release+0x138/0x260\n  __fput+0x1df/0x4b0\n  fput_close_sync+0xd2/0x170\n  __x64_sys_close+0x55/0x90\n  do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87)\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ocfs2: rebase copied fsdlm LVB pointers in locking_state","id":"CVE-2026-74351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails","id":"CVE-2026-74352"},"packages":[],"prev":{"headline":"ocfs2: validate fast symlink target during inode read","id":"CVE-2026-74350"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel OCFS2 filesystem allows local attackers to cause a denial of service or potentially execute code via debugfs.","url":"https://insights.sbomify.com/CVE-2026-74351/"}