ParcheSin parcheEl fabricante no ha publicado corrección
Exposición4 dDesde la divulgación, 16 nov 2026, 4:59 a. m.
Detección8 minDesde la divulgación hasta su ingreso al índice
Timeline
Ciclo de vida de la vulnerabilidad
Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Monitoreo
Detectada +2
Verificada
16 nov 26
19 nov 26
21 nov 26
16 nov 26
17 nov 26
18 nov 26
19 nov 26
21 nov 26
Fecha
Fase
Evento
Detalle
Divulgación
Publicada
CVE-2026-99310 divulgada · CVSS 9.8 (CNA)
Monitoreo
Detectada
Ingresó al índice
Monitoreo
Fuente: NIST NVD
Registro visto por primera vez en NIST NVD
Monitoreo
Fuente: ENISA EUVD
Registro visto por primera vez en ENISA EUVD
Divulgación
Modificada
Última actualización del registro
Monitoreo
Verificada
Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 19 nov 2026
A flaw in the Linux kernel's NFS server (nfsd) can cause a use-after-free memory error when it handles a client identification request with mismatched credentials at the same time as another request is freeing client state. An attacker can reach it remotely over the network without logging in, which could let them take control of the system or crash it.
Affects the Linux kernel NFS server (nfsd) with NFSv4 clients that have open owners, when an EXCHANGE_ID with mismatched credentials runs while an open owner is freed. No fixed versions are listed.
¿Qué significa?The nfsd function client_has_openowners() walks a client's open owner list without holding clp->cl_lock. A concurrent EXCHANGE_ID with mismatched credentials can then use memory of an nfs4_openowner after it is freed, which can cause memory corruption, kernel code execution, information disclosure or a kernel panic.
¿Quién está afectado?The facts cover the Linux kernel NFS server (nfsd) handling NFSv4 clients with open owners; no version ranges are given. A reader can check whether the NFS server is in use on a host and which kernel version is running (for example with uname -r), then compare it against the kernel vendor's advisory.
¿Qué hacer?The facts name no fixed version or patch id. Check the Linux kernel stable releases or the distribution's security advisory for a kernel containing the change that holds cl_lock in client_has_openowners().
no-patchThe facts give no workaround. Limiting the affected feature, meaning the NFSv4 server (nfsd), to hosts and clients that need it reduces exposure until an updated kernel is available.
Descripción original del registro (Linux)
In the Linux kernel, the following vulnerability has been resolved:
nfsd: hold cl_lock in client_has_openowners()
client_has_openowners() walks clp->cl_openowners and reads so_stateids
without clp->cl_lock. nfs4_put_stateowner() unhashes that openowner under
cl_lock and then frees it, so a concurrent EXCHANGE_ID with mismatched
creds can use-after-free the nfs4_openowner.
BUG: KASAN: slab-use-after-free in client_has_state+0x10a/0x140
fs/nfsd/nfs4state.c:3718 client_has_openowners()
nfsd4_exchange_id
nfsd4_proc_compound
nfsd_dispatch
svc_process
Take clp->cl_lock while client_has_openowners() walks the openowner
list.
Contexto
Condiciones y alcance
Condiciones necesarias para que el fallo sea explotable
01
Linux kernel NFS server (nfsd) handling NFSv4 clients with open owners“client_has_openowners() walks clp->cl_openowners and reads so_stateids
without clp->cl_lock.”
02
A concurrent EXCHANGE_ID with mismatched credentials runs while an open owner is being freed“so a concurrent EXCHANGE_ID with mismatched
creds can use-after-free the nfs4_openowner.”
¿Quién debe revisar?Teams running the Linux kernel NFS server (nfsd) with NFSv4 clients, on kernels that lack the cl_lock fix in client_has_openowners().
Vector CVSS 3.1
Desglose de métricas
Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones
Versiones afectadas
4.4
Remediación
Estado del parche por paquete
Paquete / producto
Estado
Corregida en
Desde divulgación
Última versión
Linux
Sin parche
—
—
—
Explotación
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
Registro
EscenarioAV:N - An NFSv4.1 COMPOUND carrying OP_EXCHANGE_ID reaches client_has_openowners via svc_process, nfsd_dispatch, nfsd4_proc_compound, and nfsd4_exchange_id. The walk runs when find_confirmed_client_by_name hits a client whose cl_cred fails same_creds against the RPC cred (RFC 5661 case 3), while a concurrent OP_CLOSE frees that nfs4_openowner.
AC:L - The attacker sends both sides on two TCP connections to nfsd: one AUTH_SYS uid does EXCHANGE_ID, CREATE_SESSION, and OPEN, then nfsd4_close frees the openowner through nfs4_free_ol_stateid and nfs4_put_stateowner, while a second uid's EXCHANGE_ID fails same_creds and enters client_has_openowners during that free.
PR:N - Both the mismatched EXCHANGE_ID and the OPEN/CLOSE that allocate and free the nfs4_openowner are AUTH_SYS RPCs. svcauth_unix_set_client accepts a client-asserted cr_uid, and nfsd4_exchange_id case 3 only compares that uid, gid, and groups in same_creds. No GSS principal or capability is required.
UI:N - The attacker itself sends EXCHANGE_ID, CREATE_SESSION, OPEN, CLOSE, and the second EXCHANGE_ID with a different cr_uid. No other user has to mount an export, open a file, or take any action.
S:U - The dangling pointer is to an nfs4_openowner in the host kernel nfsd client state, used from nfsd4_exchange_id. Corruption stays in that kernel and does not cross a guest-to-host or sandbox boundary.
C:H - client_has_openowners walks cl_openowners with list_for_each_entry and reads oo->oo_owner.so_stateids after nfs4_free_openowner has kmem_cache_free'd the nfs4_openowner back to openowner_slab. Reclaiming that slot makes the walk dereference attacker-controlled oo_perclient and so_stateids pointers.
I:H - nfs4_put_stateowner unhashes and kmem_cache_frees the nfs4_openowner while client_has_openowners still dereferences it. Reusing the openowner_slab slot aliases sprayed bytes with oo_perclient, so_stateids, and the embedded so_ops function pointers, a heap write and control-flow primitive.
A:H - KASAN reports a slab-use-after-free in client_has_openowners when the unlocked walk reads so_stateids of an nfs4_openowner already freed by nfs4_free_openowner. A poisoned or unmapped oo_perclient pointer oopses the nfsd thread and panics the kernel.Linux
Usamos cookies propias estrictamente necesarias para que el sitio funcione y sea seguro. Con tu permiso, también usamos almacenamiento local para recordar tus preferencias y medir el uso del sitio de forma agregada. Puedes aceptar, rechazar o configurar cada categoría, y cambiar tu decisión cuando quieras desde el enlace “Preferencias de cookies” del pie de página. Más información
Preferencias de cookies
Elige qué permites
Solo usamos tecnologías propias de este dominio. Sin publicidad ni rastreadores de terceros. Detalle en la Política de cookies.