{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23427 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23427 is a critical use after free vulnerability in Linux kernel, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23427 and fix it if it is affected.\n\nWhat it is: CVE-2026-23427 is a critical use after free vulnerability in Linux kernel, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23427 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-23427/ (Markdown: https://insights.sbomify.com/CVE-2026-23427/index.md)","id":"CVE-2026-23427","markdown":"https://insights.sbomify.com/CVE-2026-23427/index.md","name":"CVE-2026-23427","record":{"aliases":["BELL-CVE-2026-23427","DEBIAN-CVE-2026-23427","GHSA-vrjp-x986-3fqm","ROOT-OS-DEBIAN-13-CVE-2026-23427","UBUNTU-CVE-2026-23427"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free in the Linux kernel's ksmbd SMB server allows attackers to trigger memory corruption, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in durable v2 replay of active file handles\n\nparse_durable_handle_context() unconditionally assigns dh_info-\u003efp-\u003econn\nto the current connection when handling a DURABLE_REQ_V2 context with\nSMB2_FLAGS_REPLAY_OPERATION. ksmbd_lookup_fd_cguid() does not filter by\nfp-\u003econn, so it returns file handles that are already actively connected.\nThe unconditional overwrite replaces fp-\u003econn, and when the overwriting\nconnection is subsequently freed, __ksmbd_close_fd() dereferences the\nstale fp-\u003econn via spin_lock(\u0026fp-\u003econn-\u003ellist_lock), causing a\nuse-after-free.\n\nKASAN report:\n\n[    7.349357] ==================================================================\n[    7.349607] BUG: KASAN: slab-use-after-free in _raw_spin_lock+0x75/0xe0\n[    7.349811] Write of size 4 at addr ffff8881056ac18c by task kworker/1:2/108\n[    7.350010]\n[    7.350064] CPU: 1 UID: 0 PID: 108 Comm: kworker/1:2 Not tainted 7.0.0-rc3+ #58 PREEMPTLAZY\n[    7.350068] 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\n[    7.350070] Workqueue: ksmbd-io handle_ksmbd_work\n[    7.350083] Call Trace:\n[    7.350087]  \u003cTASK\u003e\n[    7.350087]  dump_stack_lvl+0x64/0x80\n[    7.350094]  print_report+0xce/0x660\n[    7.350100]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[    7.350101]  ? __pfx___mod_timer+0x10/0x10\n[    7.350106]  ? _raw_spin_lock+0x75/0xe0\n[    7.350108]  kasan_report+0xce/0x100\n[    7.350109]  ? _raw_spin_lock+0x75/0xe0\n[    7.350114]  kasan_check_range+0x105/0x1b0\n[    7.350116]  _raw_spin_lock+0x75/0xe0\n[    7.350118]  ? __pfx__raw_spin_lock+0x10/0x10\n[    7.350119]  ? __call_rcu_common.constprop.0+0x25e/0x780\n[    7.350125]  ? close_id_del_oplock+0x2cc/0x4e0\n[    7.350128]  __ksmbd_close_fd+0x27f/0xaf0\n[    7.350131]  ksmbd_close_fd+0x135/0x1b0\n[    7.350133]  smb2_close+0xb19/0x15b0\n[    7.350142]  ? __pfx_smb2_close+0x10/0x10\n[    7.350143]  ? xas_load+0x18/0x270\n[    7.350146]  ? _raw_spin_lock+0x84/0xe0\n[    7.350148]  ? __pfx__raw_spin_lock+0x10/0x10\n[    7.350150]  ? _raw_spin_unlock+0xe/0x30\n[    7.350151]  ? ksmbd_smb2_check_message+0xeb2/0x24c0\n[    7.350153]  ? ksmbd_tree_conn_lookup+0xcd/0xf0\n[    7.350154]  handle_ksmbd_work+0x40f/0x1080\n[    7.350156]  process_one_work+0x5fa/0xef0\n[    7.350162]  ? assign_work+0x122/0x3e0\n[    7.350163]  worker_thread+0x54b/0xf70\n[    7.350165]  ? __pfx_worker_thread+0x10/0x10\n[    7.350166]  kthread+0x346/0x470\n[    7.350170]  ? recalc_sigpending+0x19b/0x230\n[    7.350176]  ? __pfx_kthread+0x10/0x10\n[    7.350178]  ret_from_fork+0x4fb/0x6c0\n[    7.350183]  ? __pfx_ret_from_fork+0x10/0x10\n[    7.350185]  ? __switch_to+0x36c/0xbe0\n[    7.350188]  ? __pfx_kthread+0x10/0x10\n[    7.350190]  ret_from_fork_asm+0x1a/0x30\n[    7.350197]  \u003c/TASK\u003e\n[    7.350197]\n[    7.355160] Allocated by task 123:\n[    7.355261]  kasan_save_stack+0x33/0x60\n[    7.355373]  kasan_save_track+0x14/0x30\n[    7.355484]  __kasan_kmalloc+0x8f/0xa0\n[    7.355593]  ksmbd_conn_alloc+0x44/0x6d0\n[    7.355711]  ksmbd_kthread_fn+0x243/0xd70\n[    7.355839]  kthread+0x346/0x470\n[    7.355942]  ret_from_fork+0x4fb/0x6c0\n[    7.356051]  ret_from_fork_asm+0x1a/0x30\n[    7.356164]\n[    7.356214] Freed by task 134:\n[    7.356305]  kasan_save_stack+0x33/0x60\n[    7.356416]  kasan_save_track+0x14/0x30\n[    7.356527]  kasan_save_free_info+0x3b/0x60\n[    7.356646]  __kasan_slab_free+0x43/0x70\n[    7.356761]  kfree+0x1ca/0x430\n[    7.356862]  ksmbd_tcp_disconnect+0x59/0xe0\n[    7.356993]  ksmbd_conn_handler_loop+0x77e/0xd40\n[    7.357138]  kthread+0x346/0x470\n[    7.357240]  ret_from_fork+0x4fb/0x6c0\n[    7.357350]  ret_from_fork_asm+0x1a/0x30\n[    7.357463]\n[    7.357513] The buggy address belongs to the object at ffff8881056ac000\n[    7.357513]  which belongs to the cache kmalloc-1k of size 1024\n[    7.357857] The buggy address is located 396 bytes inside of\n[    7.357857]  freed 1024-byte region \n---truncated---","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":"ksmbd: fix use-after-free in durable v2 replay of active file handles","id":"CVE-2026-23427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ksmbd: fix use-after-free of share_conf in compound request","id":"CVE-2026-23428"},"packages":[],"prev":{"headline":"drm/logicvc: Fix device node reference leak in logicvc_drm_config_parse()","id":"CVE-2026-23426"},"products":["Linux"],"published":"2026-04-03","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel's ksmbd SMB server allows attackers to trigger memory corruption, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-23427/"}