CVE-2026-99571
Linux kernel NULL pointer dereference in NVMe over TCP address attribute
A local user who reads the address attribute during connection error recovery can crash the system.
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-99571 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
A race in the Linux kernel's NVMe over TCP driver can cause a NULL pointer dereference when the "address" sysfs attribute is read while the admin queue is being torn down during connection error recovery. The fix checks queue state under the queue lock and ties lock lifetime to the controller.
Descripción original del registro (Linux)
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: Validate the queue state under the queue lock in the address attribute Reading the "address" sysfs attribute calls kernel_getsockname() on the admin queue socket, which can race with the queue teardown during connection error recovery: a reader can observe NVME_TCP_Q_LIVE set, then block on the queue lock while nvme_tcp_free_queue() releases the socket and clears queue->sock without holding the lock. Once the reader acquires the lock it dereferences the NULL socket pointer. Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") had the queue liveness check inside the lock. Commit 782373ba2766 ("nvme: tcp: avoid race between queue_lock lock and destroy") moved it back out because the lock itself is destroyed in nvme_tcp_free_queue(), so a reader arriving late trips mutex_destroy(). Check the queue liveness inside the queue lock, and clear queue->sock under the same lock. The teardown clears NVME_TCP_Q_LIVE under the lock well before the socket is released, so a reader either sees the bit cleared or a socket that cannot be released while it holds the lock. To also close the lock lifetime race, the queue locks are now owned by the controller: they are initialized with the queue array and only destroyed when the controller is freed, which cannot happen while a sysfs attribute read is still in progress. The queue count is computed by the NVME_TCP_OPT_NR_QUEUES() macro from the original connect options for both initialization and destruction, as reconnects may shrink ctrl->queue_count.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Linux |
Corregida | 6.2, 6.7, 6.12 | — | — |
6.26.76.12Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://git.kernel.org/stable/c/0af6a8aede3121bc9662111665294731daddb13ahttps://git.kernel.org/stable/c/2eeeaa9c1ff0c429096acc2947c296db6a56f96dLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
