{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98815 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98815 is an use after free vulnerability in Linux, published on 18 Oct 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-98815 and fix it if it is affected.\n\nWhat it is: CVE-2026-98815 is an use after free vulnerability in Linux, published on 18 Oct 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-98815 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-98815/ (Markdown: https://insights.sbomify.com/CVE-2026-98815/index.md)","id":"CVE-2026-98815","markdown":"https://insights.sbomify.com/CVE-2026-98815/index.md","name":"CVE-2026-98815","record":{"aliases":["AZL-109025","BELL-CVE-2026-98815","DEBIAN-CVE-2026-98815","GHSA-x2m3-gxmv-qw6j","UBUNTU-CVE-2026-98815"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NVMe","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel NVMe driver allows local attackers to cause a system crash or potentially escalate privileges.","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\nnvme: fix cdev lifetime\n\nSashiko bot reported a potential problem for the cdev lifetime in [0]\n- the code there is heavily based on the NVMe code.\n\nCurrently the NS head .open and .release file_operations methods take and\nput a reference to the nvme_ns_head to ensure that this structure does not\ndisappear while we open fds for that cdev.\n\nIn multipath mode, when we teardown the NS head, we call nvme_cdev_del() -\u003e\ncdev_device_del() -\u003e cdev_del(). However after cdev_del() returns, cdevs\nalready open will remain and their fops will still be callable. As such,\nwe can still reference the cdev after the nvme_ns_head reference count\ndrops to 0 (and is freed).\n\nThis can be shown with an application which delays between opening the cdev\nand issuing the ioctl while the NS head is being torn down:\n\n# ./ioctl_file /dev/ng1n1 \u0026\n# waiting 10 seconds ....\n\n# ./ini_nvme_teardown.sh\n[   21.221718] nvme nvme1: Removing ctrl: NQN \"nvme-test-target\"\n[   21.274609] nvme nvme2: Removing ctrl: NQN \"nvme-test-target\"\n# now going to issue ioctl ....\n[   26.549285] ==================================================================\n[   26.550841] BUG: KASAN: slab-use-after-free in cdev_put.part.0+0x3d/0x40\n[   26.552352] Read of size 8 at addr ffff88811e7fa170 by task ioctl_file/237\n[   26.553805]\n[   26.554227] CPU: 3 UID: 0 PID: 237 Comm: ioctl_file Not tainted 7.2.0-rc1-00004-g6852a10e32d4 #921 PREEMPT(lazy)\n[   26.554236] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   26.554241] Call Trace:\n[   26.554245]  \u003cTASK\u003e\n[   26.554248]  dump_stack_lvl+0x68/0xa0\n[   26.554266]  print_report+0x10d/0x5d0\n[   26.554276]  ? __virt_addr_valid+0x21d/0x3f0\n[   26.554287]  ? cdev_put.part.0+0x3d/0x40\n[   26.554292]  kasan_report+0x96/0xd0\n[   26.554300]  ? cdev_put.part.0+0x3d/0x40\n[   26.554307]  cdev_put.part.0+0x3d/0x40\n[   26.554313]  __fput+0x7bc/0xa70\n[   26.554322]  fput_close_sync+0xd8/0x190\n[   26.554328]  ? __pfx_fput_close_sync+0x10/0x10\n[   26.554337]  __x64_sys_close+0x79/0xd0\n[   26.554344]  do_syscall_64+0x117/0x6b0\n[   26.554351]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   26.554358] RIP: 0033:0x7f938c067727\n[   26.554364] Code: 48 89 fa 4c 89 df e8 28 ad 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 \u003c5bf\n[   26.554369] RSP: 002b:00007fff49f05980 EFLAGS: 00000202 ORIG_RAX: 0000000000000003\n[   26.554376] RAX: ffffffffffffffda RBX: 00007f938bfd7780 RCX: 00007f938c067727\n[   26.554380] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n[   26.554383] RBP: 00007fff49f05a10 R08: 0000000000000000 R09: 0000000000000000\n[   26.554386] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000\n[   26.554389] R13: 00007fff49f05b40 R14: 00007f938c207000 R15: 000055c148471d78\n[   26.554397]  \u003c/TASK\u003e\n[   26.554399]\n[   26.575612] Allocated by task 100:\n[   26.575871]  kasan_save_stack+0x24/0x50\n[   26.576157]  kasan_save_track+0x14/0x30\n[   26.576418]  __kasan_kmalloc+0x7f/0x90\n[   26.576668]  __kmalloc_noprof+0x281/0x6c0\n[   26.576938]  nvme_alloc_ns+0x7f7/0x3170\n[   26.577206]  nvme_scan_ns+0x508/0x880\n[   26.577449]  async_run_entry_fn+0x8c/0x350\n[   26.577723]  process_scheduled_works+0xb6f/0x1a00\n[   26.578034]  worker_thread+0x4ad/0xb40\n[   26.578283]  kthread+0x34f/0x450\n[   26.578501]  ret_from_fork+0x563/0x800\n[   26.578752]  ret_from_fork_asm+0x1a/0x30\n[   26.579012]\n[   26.579124] Freed by task 237:\n[   26.579335]  kasan_save_stack+0x24/0x50\n[   26.579596]  kasan_save_track+0x14/0x30\n[   26.579855]  kasan_save_free_info+0x3a/0x60\n[   26.580131]  __kasan_slab_free+0x43/0x70\n[   26.580388]  kfree+0x321/0x500\n[   26.580591]  nvme_ns_head_chr_release+0x39/0x50\n[   26.580883]  __fput+0x352/0xa70\n[   26.581095]  fput_close_sync+0xd8/0x190\n[   26.581350]  __x64_sys_close+0x79/0xd0\n[   26.581595]  do_syscall_64+0x117/0x6b0\n[   26.581842]  entry_SYSCAL\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":"nvme: fix cdev lifetime","id":"CVE-2026-98815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"bpf: Fix overflow of jump offset in constant blinding","id":"CVE-2026-98816"},"packages":[],"prev":{"headline":"nvme: fix command effects log lifetime for multipath heads","id":"CVE-2026-98814"},"products":["Linux"],"published":"2026-10-18","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-10-26","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel NVMe driver allows local attackers to cause a system crash or potentially escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-98815/"}