llamaCVEVulnerability Intelligence
/
zephyr

CVE-2026-87040

zephyr buffer overflow

UnclearParche disponiblebuffer overflow
Descargar PNG JSON
CVSS 3.1
8.3
Alta
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versiones4.3.2 · 4.5.0
Exposición15 dDesde la divulgación, 4 nov 2026, 1:09 a. m.
Detección5 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: OSV
Verificada
4 nov 26
9 nov 26
16 nov 26
19 nov 26
4 nov 26
8 nov 26
11 nov 26
15 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-87040 divulgada · CVSS 8.3 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
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

The nRF link-layer receive paths of the open-source Bluetooth LE Controller did not validate the on-air LENGTH field of a received PDU against the maximum receive length that was used to program the radio. isr_rx_pdu() in subsys/bluetooth/controller/ll_sw/nordic/lll/lll_conn.c enqueued any non-empty data PDU after only the sequence-number and (for encrypted links) MIC checks, and the corresponding isr_rx() handlers in lll_central_iso.c, lll_peripheral_iso.c, lll_sync_iso.c and lll_scan_aux.c did the same for ISO and extended-advertising PDUs. The nRF radio stores the received header verbatim and truncates only the payload at PCNF1.MAXLEN, so a frame declaring more octets than were configured leaves a node buffer whose len field describes more data than the buffer holds. An attacker within radio range that can emit a hand-crafted link-layer PDU — for a connection, any peer that establishes an unencrypted LE connection to a connectable advertiser; for CONFIG_BT_CTLR_SYNC_ISO, any broadcaster the device is synchronised to — can set the length byte up to 255 while the controller has programmed a much smaller maximum (lll->dle.eff.max_rx_octets, which is 27 until a Data Length Update, or the negotiated cis_lll->rx.max_pdu). No pairing, authentication or user interaction is required. On encrypted links the CCM MIC check normally rejects such a frame first, so the exposure is on unencrypted traffic, which is why the added check is placed after decryption. The unchecked length reaches hci_acl_encode() in subsys/bluetooth/controller/hci/hci.c, which performs net_buf_add(buf, pdu_data->len) followed by a memcpy() of that many bytes out of the node_rx pool element. Because CONFIG_BT_CTLR_DATA_LENGTH_MAX and CONFIG_BT_BUF_ACL_RX_SIZE both default to 27, this is an out-of-bounds read of up to roughly 228 bytes past the received PDU and a corresponding out-of-bounds write past the HCI ACL buffer into neighbouring buffers of the same pool; the tailroom test in net_buf_simple_add() is only enforced when CONFIG_NET_BUF_HARDENING (or CONFIG_ASSERT) is enabled. On the ISO paths the same unchecked length makes isoal_rx_append_to_sdu() read past the ISO node buffer and emit adjacent controller RAM to the host as ISO data. The practical result is remote memory corruption and controller crashes, plus disclosure of controller memory into the host data path. The fix rejects any received PDU whose length exceeds the value that was used to configure the radio reception. Note that lll_sync.c (periodic advertising sync reception) was not changed and still enqueues received PDUs without an equivalent bound.

Affects Zephyr Bluetooth LE Controller (nRF link layer) 1.6.0 up to 4.3.2 and 4.4.0 up to 4.5.0, mainly on unencrypted links. Fixed in 4.3.2 and 4.5.0.

¿Qué significa?The controller accepts incoming Bluetooth LE packets whose length field is larger than the configured maximum receive length, so it reads and writes memory outside the intended buffer. The result can be memory corruption, controller crashes, and controller memory leaking into the host data path.
¿Quién está afectado?Zephyr Bluetooth LE Controller (nRF link layer) versions from 1.6.0 up to 4.3.2, and from 4.4.0 up to 4.5.0. The exposure is mainly on unencrypted traffic, because encrypted links normally reject such frames at the MIC check first. For ISO/broadcast paths, check whether the device is synchronised to a broadcaster and whether CONFIG_BT_CTLR_SYNC_ISO is enabled.
¿Qué hacer?Upgrade to Zephyr 4.3.2 for the 4.3 line or 4.5.0 for the 4.5 line.
fix-completeThe advisory describes the fix as partial, so the listed fixed versions may not close every affected path. The facts do not say which paths remain unfixed.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Zephyr Bluetooth LE Controller (nRF link layer) affected versions >= 1.6.0 and < 4.3.2, or >= 4.4.0 and < 4.5.0“Affected versions >= 1.6.0, < 4.3.2 >= 4.4.0, < 4.5.0”
02
Connection is unencrypted (on encrypted links the MIC check normally rejects the frame first)“On encrypted links the CCM MIC check normally rejects such a frame first, so the exposure is on unencrypted traffic”
03
For ISO/broadcast paths, the device must be synchronised to a broadcaster with CONFIG_BT_CTLR_SYNC_ISO enabled“for CONFIG_BT_CTLR_SYNC_ISO , any broadcaster the device is synchronised to”
El parche publicado es parcial: verifique el advisory del fabricante.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:A
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
zephyr≥ 1.6.0 < 4.3.2
zephyr≥ 4.4.0 < 4.5.0
1.6.0
4.3.2
4.4.0
4.5.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
zephyr
Corregida 4.3.2, 4.5.0 — —
Versiones corregidas4.3.24.5.0
Explotación

Arsenal público

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

Referencias
Fabricantehttps://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-grqr-q9fh-8ff2
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/8ca41216e8e47a018e52044992789b5011ac99aa

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