llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99765

Linux kernel use-after-free in SCSI target demo-mode ACL entries

An unauthenticated initiator can trigger memory corruption by logging in to a demo-mode target.

Texto original en inglés · Ver en español

Parche disponiblescsi
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche6 versiones3.11 · 3.19 · 4.2 · 4.5 …
Exposición1 dDesde la divulgación, 20 nov 2026, 12:51 a. m.
Detección22 minDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Sin puntaje CVSS ni severidad publicados y sin explotación conocida. Estimación de Llama (sin evaluación oficial): remediar en el mantenimiento regular y revisar si la fuente publica más datos. Hay versiones corregidas disponibles.
Si todas fueran así, viviría en la playa.Si todo fuera así, el SOC dormiría ocho horas.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
Verificada
12:51 a. m.
01:13 a. m.
02:11 a. m.
11:55 a. m.
12:51 a. m.
09:37 a. m.
06:23 p. m.
03:09 a. m.
11:55 a. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99765 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
Resumen

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown A demo-mode (generate_node_acls=1) login that allocates a dynamic NodeACL populates that ACL's per-LUN dev entries in core_tpg_add_node_to_devs() *before* the ACL is linked onto tpg->acl_node_list by target_add_node_acl(): core_tpg_check_initiator_node_acl(): ... core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */ target_add_node_acl(acl); /* only now listed */ The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only tpg->acl_node_list, so a dev entry whose ACL is still in the window above is invisible to the sweep and is never disabled. It is left on the se_lun->lun_deve_list after core_tpg_remove_lun() frees the se_lun; when the same unpacked_lun is later re-added and the se_lun is reallocated at the same address, the stale dev entry is rediscovered by target_nacl_find_deve() and core_enable_device_list_for_node() corrupts lun_deve_list: BUG: KASAN: slab-use-after-free ... core_enable_device_list_for_node+0x5ce/0x880 core_tpg_add_node_to_devs+0x169/0x190 core_dev_add_lun+0x146/0x190 target_fabric_port_link+0xe9/0x1b0 configfs_symlink+0x381/0xae0 __x64_sys_symlink+0x55/0x80 The demo-mode login path that drives the ACL/dev-entry creation is reachable by an unauthenticated initiator; the colliding LUN add/remove is a local configfs operation. Commit 49cb77e297dc ("target: Avoid mappedlun symlink creation during lun shutdown") introduced se_lun->lun_shutdown and guarded the *explicit* ACL MappedLUN path (target_fabric_mappedlun_link()), but the demo-mode automatic path, core_tpg_add_node_to_devs() -> core_enable_device_list_for_node(), was never given the equivalent guard, and the publish-after-populate ordering in core_tpg_check_initiator_node_acl() was left unchanged. Fix it in three cooperating parts: 1) Publish the dynamic NodeACL onto acl_node_list *before* creating its dev entries, so the teardown sweep can observe them. 2) Refuse to attach a dev entry to an se_lun that is shutting down, checked under nacl->lun_entry_mutex -- the same lock the sweep takes -- so once the sweep has passed an ACL any later enable for that LUN observes lun_shutdown and skips it. 3) In core_enable_device_list_for_node(), insert the new dev entry onto lun->lun_deve_list while still holding nacl->lun_entry_mutex, in both the replace and the new-entry branch. Previously the entry was added to nacl->lun_entry_hlist under the mutex but to lun->lun_deve_list only after dropping it; with the ACL now published early, the sweep could take the mutex in that gap, find the entry on the hlist, core_disable_device_list_for_node() it (list_del() on the not-yet- linked lun_link succeeds and the entry is freed), and then the enable would list_add_tail() the freed entry back onto lun_deve_list. Linking both lists under the mutex makes enable and the sweep mutually exclusive, closing that window. core_tpg_add_node_to_devs() already ignores the return value of core_enable_device_list_for_node(), so a shutting-down LUN is simply skipped.

Versiones

Rangos afectados

Afectada Corregida
Linux≥ 3.10.108 < 3.11
Linux≥ 3.18.64 < 3.19
Linux≥ 4.1.47 < 4.2
Linux≥ 4.4.81 < 4.5
Linux≥ 4.9.24 < 4.10
Linux≥ 4.10.12 < 4.11
3.10.108
3.11
3.18.64
3.19
4.1.47
4.2
4.4.81
4.5
4.9.24
4.10
4.10.12
4.11
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 3.11, 3.19, 4.2, 4.5, 4.10, 4.11 — —
Versiones corregidas3.113.194.24.54.104.11
Explotación

Arsenal público

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

Referencias
Otrahttps://git.kernel.org/stable/c/c8b6eec86742f736a913aba7d7c1d0cedb1d7751
Otrahttps://git.kernel.org/stable/c/78ad4413fab0cbd42c7280b5069ed2dd3f039162
Otrahttps://git.kernel.org/stable/c/6a6e7d7230cd4e0a6c003bae5b85bf37a1e77b94

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