llamaCVEVulnerability Intelligence
/
Zephyr

CVE-2026-77685

Zephyr out-of-bounds read in Bluetooth RFCOMM

A nearby attacker can send one malformed frame with no login to leak adjacent memory and crash the Bluetooth host.

UnclearParche disponibleout-of-bounds read
Descargar PNG JSON
CVSS 3.1
8.3
Alta
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión4.5.0
Exposición8 dDesde la divulgación, 10 nov 2026, 5:07 p. m.
Detección16 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. 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
Fuente: OSV
Verificada
10 nov 26
13 nov 26
16 nov 26
19 nov 26
10 nov 26
13 nov 26
15 nov 26
17 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-77685 divulgada · CVSS 8.3 (CNA)
Monitoreo Detectada Ingresó al índice
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
Resumen generado por IA · CC-BY 4.0 · 10 nov 2026

The Bluetooth Classic RFCOMM component is affected. A nearby device can send a single malformed RFCOMM frame, without logging in or any user action, to make the device leak about 255 bytes of adjacent memory and corrupt adjacent memory, which can crash the Bluetooth host.

Affects Zephyr 1.7.0 up to 4.5.0 with CONFIG_BT_RFCOMM enabled, from peers that do not claim host Secure Simple Pairing support. Fixed in 4.5.0.

¿Qué significa?The MCC TEST command handler in Bluetooth Classic RFCOMM has an integer underflow. A remote peer can use it to read about 255 bytes of adjacent stack or pool memory and trigger an out-of-bounds write that can crash the Bluetooth host.
¿Quién está afectado?Zephyr 1.7.0 up to 4.5.0 with CONFIG_BT_RFCOMM enabled, which SPP, HFP, HSP, GOEP and similar profiles all enable. The issue involves peers that do not claim host Secure Simple Pairing support. To check, look at the Zephyr version in use and whether CONFIG_BT_RFCOMM is enabled in the build configuration.
¿Qué hacer?Upgrade to Zephyr 4.5.0, the fixed version.
fix-completeThe checked facts mark the fix as partial but do not say what remains unfixed. Check the advisory for details before treating 4.5.0 as a complete fix.
Descripción original del registro (zephyr)

The RFCOMM multiplexer control-channel handler in subsys/bluetooth/host/classic/rfcomm.c computed the echo length for a BT_RFCOMM_TEST command as buf->len - 1 and passed it to rfcomm_send_test(), whose length parameter is a uint8_t. A malformed but FCS-valid UIH frame on DLCI 0 can leave buf->len == 0 after rfcomm_handle_msg() pulls the two-byte MCC header, so buf->len - 1 underflows and narrows to 255. rfcomm_send_test() then copies 255 bytes out of a receive buffer that holds no remaining valid data, and appends them to an outgoing L2CAP PDU allocated with only CONFIG_BT_L2CAP_TX_MTU (253 by default for CONFIG_BT_CLASSIC) bytes of tailroom. The source read runs past the end of the ACL receive buffer into adjacent buffers of the same net_buf pool, and the destination copy overruns the transmit buffer by about eight bytes; net_buf_add_mem() performs no runtime bounds check in ordinary builds, where the underlying __ASSERT_NO_MSG() is compiled out. The trigger is a single five-byte RFCOMM frame on the multiplexer control channel, which is processed as soon as the L2CAP channel for PSM 3 is established — before any DLC exists and independent of RFCOMM session state. bt_rfcomm_init() registers that L2CAP server with .sec_level = BT_SECURITY_L1, which l2cap_br_conn_security() accepts without any link key from a peer that does not claim host Secure Simple Pairing support, so an unpaired BR/EDR device in radio range of a connectable target with CONFIG_BT_RFCOMM enabled (SPP, HFP, HSP, GOEP and similar profiles all enable it) can reach the defect. The resulting 255-byte TEST response is transmitted back to the attacker, disclosing roughly 255 bytes of adjacent stack/pool memory — including the contents of neighbouring receive buffers, which an attacker can prime with earlier packets — and the accompanying out-of-bounds write corrupts memory following the transmit buffer, which can crash the Bluetooth host. The request is trivially repeatable, so both the disclosure and the corruption can be driven at will. Two fixes are needed, and the first on its own does not close the out-of-bounds write. Fix 1 (0040ef781e1d, #115768) strips the FCS byte in rfcomm_recv() and echoes buf->len, rejecting anything over UINT8_MAX, which removes the underflow and the over-read. But rfcomm_make_uih_msg() still allocates the response with bt_l2cap_create_pdu() and never compares the requested length with the buffer's tailroom, so a well-formed TEST command carrying a pattern of about 248 bytes or more still builds a response (3-byte frame header, 2-byte message header, pattern, FCS) larger than the 253 bytes available. A pattern that long can only be received when the RFCOMM L2CAP receive MTU (CONFIG_BT_RFCOMM_L2CAP_MTU, which defaults to CONFIG_BT_BUF_ACL_RX_SIZE) exceeds CONFIG_BT_L2CAP_TX_MTU. The plain BR/EDR defaults (200 against 253) cannot reach it, but from v4.3.0 enabling CONFIG_BT_GOEP raises CONFIG_BT_BUF_ACL_RX_SIZE to 264 (265 from v4.4.0), so GOEP builds with only fix 1 applied still overrun the transmit buffer by up to eight bytes. This includes v4.3.2, the last v4.3 release, which carries fix 1 but will not receive fix 2. Fix 2 (214530895dd3, #118293) checks the tailroom on every RFCOMM PDU allocation and closes this residual write.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Zephyr versions 1.7.0 up to 4.5.0 (fixed in 4.5.0)“>= 1.7.0, < 4.5.0”
02
CONFIG_BT_RFCOMM enabled“with CONFIG_BT_RFCOMM enabled (SPP, HFP, HSP, GOEP and similar profiles all enable it)”
03
Peer does not claim host Secure Simple Pairing support“from a peer that does not claim host Secure Simple Pairing support”
¿Quién debe revisar?Teams shipping Zephyr 1.7.0 through 4.4.x with CONFIG_BT_RFCOMM enabled, such as SPP, HFP, HSP or GOEP builds.
No protegeApplying only the first fix does not close the out-of-bounds write.
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:H
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
zephyr≥ 1.7.0 < 4.5.0
1.7.0
4.5.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
zephyr
Corregida 4.5.0 — —
Versiones corregidas4.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-mhhp-8w67-cggv
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/0040ef781e1d705066045850782cd8efa5beaa02
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/214530895dd327ef34468fb25e132df6976e927c

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