llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99277

Linux kernel use-after-free in ksmbd session channel tracking

Freed connections can still be used in session handling, but what an attacker could gain is not yet known.

Specific setups onlyParche disponibleksmbd
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión7.3
Exposición11 dDesde la divulgación, 7 nov 2026, 9:08 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 +1
Fuente: OSV
Verificada
7 nov 26
10 nov 26
16 nov 26
19 nov 26
7 nov 26
10 nov 26
13 nov 26
16 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99277 divulgada · CVSS 7.5 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 7 nov 2026

The Linux kernel's ksmbd SMB server has a use-after-free flaw in how it tracks session channels: a connection can be freed while another session reference is still using it. The provided data does not state what an attacker can gain or how they would reach the flaw, so no attack vector can be described.

¿Qué significa?The ksmbd SMB server can free a connection object while a session still uses it. Later use of that freed memory can disclose kernel memory, corrupt memory, or crash the kernel. The fix holds a connection reference for each session channel.
¿Quién está afectado?The product data lists Linux kernel ranges from 7.2.8 up to a fix in 7.3, and Kernel 7.3.0 up to 7.3.2, and these ranges do not agree on the exact fixed version. To check a system, run uname -r for the kernel version and confirm whether ksmbd is serving SMB3 with multichannel enabled, since the vulnerable path runs only in that case.
¿Qué hacer?Update to a kernel release at or after the fixed version named in the product data, using your distribution's kernel packages. Because the sources disagree on the fixed version, prefer the newest available kernel update from your vendor.
Descripción original del registro (Linux)

In the Linux kernel, the following vulnerability has been resolved: ksmbd: hold a connection reference for each session channel ksmbd_session_unregister() removes a session from the global and per- connection tables before dropping the table reference. A concurrent reference holder can keep the session and its channel list alive after those removals. Connection cleanup can no longer find the unpublished session to remove its channels. Since a channel only stores a raw conn pointer, the connection can be freed while another session reference holder is still accessing it, for example during SMB3.1.1 binding or a procfs read. Take a connection reference when registering a channel and release it on insertion failure, channel removal, or final session destruction. Keep the channels and signing keys until the session is destroyed so a response can still be signed after the session has been unregistered.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
SMB 3.1.1 binding path reached only when SMB3 multichannel is enabled“entered only when KSMBD_GLOBAL_FLAG_SMB3_MULTICHANNEL is already set”
02
Session is unregistered during a Kerberos reauthentication after kerberos_expiry has passed“drops an established session only after session_setup_reauth sets SMB2_SESSION_IN_PROGRESS because sess->kerberos_expiry has passed”
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:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
Linux≥ 7.2.8 < 7.3
Kernel≥ 7.3.0 < 7.3.2
7.2.8
7.3
7.3.0
7.3.2
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 7.3 — —
Versiones corregidas7.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Registro
EscenarioAV:N - register_session_channel() runs from smb2_sess_setup() after ksmbd_conn_handler_loop() queues an SMB2 SESSION_SETUP read from the TCP socket. That command stores the connection in chann->conn without a reference; a later failing SESSION_SETUP calls ksmbd_session_unregister(), and ksmbd_conn_free() can free it while the channel still points at it. AC:H - ksmbd_session_unregister() drops an established session only after session_setup_reauth sets SMB2_SESSION_IN_PROGRESS because sess->kerberos_expiry has passed. The attacker's chann->conn->cipher_type read is smb2_sess_setup()'s SMB 3.1.1 binding arm, entered only when KSMBD_GLOBAL_FLAG_SMB3_MULTICHANNEL is already set, immediately after ksmbd_session_lookup_slowpath(), with no delay the attacker can hold across __ksmbd_conn_release_work(). PR:L - register_session_channel() writes chann->conn only after ntlm_authenticate() or krb5_authenticate() succeeds, and the reauth path that unregisters a session which already has channels depends on kerberos_expiry set by ksmbd_krb5_authenticate(). A SESSION_SETUP rejected before authentication stores no channel. UI:N - The client sends the SESSION_SETUP that registers the channel, the failing reauth SESSION_SETUP that calls ksmbd_session_unregister(), and the TCP close that reaches ksmbd_server_terminate_conn() and ksmbd_conn_free(). S:U - The freed object is a ksmbd_conn in the host kernel that serves this SMB session, so the corruption stays in that kernel security authority. C:H - __ksmbd_conn_release_work() kfree_sensitive()s the conn while the channel keeps the pointer. smb2_sess_setup() then reads chann->conn->cipher_type, and show_proc_session() follows chan->conn->vals and inet_addr; reclaiming the slab lets those uses disclose the replacement object. I:H - show_proc_session() down_read()s chan->conn->session_lock through the channel's raw pointer after the connection can already have been freed, writing the rwsem of whatever reused that slot. The use-after-free of ksmbd_conn is a heap write against that allocation. A:H - smb2_sess_setup()'s read of chann->conn->cipher_type and show_proc_session()'s lock of chan->conn->session_lock both use the ksmbd_conn after __ksmbd_conn_release_work() freed it, which oopses the kernel.Linux
Referencias
Fabricantehttps://git.kernel.org/stable/c/4b333aed69cfc2c8687b86b6a4364a0dffc16dd8
Fabricantehttps://git.kernel.org/stable/c/add8d7fb04efe564193df73581889c62fc0016f1

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.