CVE-2026-99516 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

nvmet-fc: fix use-after-free in nvmet_fc_ls_create_connection()

nvmet_fc_ls_create_connection() looks up the association with nvmet_fc_find_target_assoc(), which returns it with a reference held, and drops that reference as soon as the target queue has been allocated. iod->assoc is then dereferenced again by nvmet_fc_makeconnid() while building the connection id.

The queue only borrows the pointer and takes no reference of its own. Once the lookup reference is dropped the association is kept alive solely by the reference taken when it was created, so a disconnect LS or a remote port unregister running concurrently can free it before nvmet_fc_makeconnid() reads it:

BUG: KASAN: slab-use-after-free in nvmet_fc_handle_ls_rqst_work (drivers/nvme/target/fc.c:193 drivers/nvme/target/fc.c:1841 drivers/nvme/target/fc.c:1995 drivers/nvme/target/fc.c:2021) Read of size 8 at addr ffff888179f1b000 by task kworker/u9:2/1167

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 Workqueue: nvmet-wq nvmet_fc_handle_ls_rqst_work Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) nvmet_fc_handle_ls_rqst_work (drivers/nvme/target/fc.c:193 drivers/nvme/target/fc.c:1841 drivers/nvme/target/fc.c:1995 drivers/nvme/target/fc.c:2021) process_scheduled_works (kernel/workqueue.c:3322 kernel/workqueue.c:3405) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (archkernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) </TASK>

Freed by task 1167 on cpu 0 at 405.998150s: kasan_save_track (mm/kasan/common.c:57 mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/generic.c:584) __kasan_slab_free (mm/kasan/common.c:253 mm/kasan/common.c:285) kfree (include/linux/kasan.h:235 mm/slub.c:2705 mm/slub.c:6405 mm/slub.c:6720) nvmet_fc_handle_ls_rqst_work (drivers/nvme/target/fc.c:1808 drivers/nvme/target/fc.c:1995 drivers/nvme/target/fc.c:2021) process_scheduled_works (kernel/workqueue.c:3322 kernel/workqueue.c:3405) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (archkernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

The buggy address belongs to the object at ffff888179f1b000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 0 bytes inside of freed 2048-byte region [ffff888179f1b000, ffff888179f1b800)

Hold the lookup reference until the response has been built, and drop it on the error path as well.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel contains a critical use-after-free vulnerability within the NVMe over Fibre Channel (nvmet-fc) subsystem, specifically in the function nvmet_fc_ls_create_connection(). This flaw arises from improper reference counting management when handling Link Service requests. The function initially retrieves a target association object via nvmet_fc_find_target_assoc(), which correctly increments the reference count to ensure the object remains valid during access. However, the code prematurely releases this reference immediately after allocating the target queue, under the assumption that the queue holds its own independent reference or lifetime guarantee. In reality, the queue merely borrows a pointer to the association without acquiring an additional reference. Consequently, if any concurrent operation such as a disconnect Link Service command or remote port unregistration occurs between the release of the lookup reference and the subsequent access by nvmet_fc_makeconnid(), the underlying memory structure can be freed while still being accessed.

This race condition leads to a kernel slab-use-after-free error, detected via Kernel Address Sanitizer (KASAN). The vulnerability allows for out-of-bounds reads or arbitrary code execution if an attacker can control the timing of concurrent disconnect events against a target port. The operational impact includes potential system crashes, denial of service through kernel panic, and potentially privilege escalation if the freed memory is reallocated to hold sensitive data that is then read by the vulnerable function. The stack trace indicates the fault occurs during workqueue processing in nvmet_fc_handle_ls_rqst_work, highlighting the asynchronous nature of Fibre Channel link management tasks which exacerbates the timing window for exploitation.

From a classification perspective, this vulnerability aligns with CWE-416: Use After Free, where memory is accessed after it has been freed due to incorrect lifecycle management. In terms of adversarial tactics, this could be leveraged within ATT&CK technique T1059: Command and Scripting Interpreter or T1203: Exploitation for Credential Access if the resulting instability leads to information disclosure through kernel memory dumps. The root cause is a failure in maintaining object lifetime guarantees during concurrent state transitions in network-facing subsystems, which is particularly dangerous given that Fibre Channel targets often handle high-volume I/O and frequent connection management operations from multiple initiators.

To mitigate this vulnerability, the reference count acquired by nvmet_fc_find_target_assoc() must be held until the entire response structure has been fully constructed, including the execution of nvmet_fc_makeconnid(). The fix involves deferring the release of the association object to ensure that no concurrent disconnect or unregister operation can free it while it is still in use. Additionally, error handling paths must explicitly drop this reference to prevent memory leaks if an early exit occurs before completion. System administrators should apply kernel updates containing this patch immediately and monitor for any signs of instability related to Fibre Channel target operations. Regular auditing of concurrent access patterns in network subsystems can help identify similar race conditions before they are exploited.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00174

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!