Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

msrc логотип

CVE-2026-90255

Опубликовано: 19 сент. 2026
Источник: msrc
CVSS3: 7.1
EPSS Низкий

Описание

Bluetooth: hci_conn: fix the SCO setup context lifetime

Обновления

ПродуктСтатьяОбновление
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0

Показывать по

EPSS

Процентиль: 28%
0.00341
Низкий

7.1 High

CVSS3

Связанные уязвимости

CVSS3: 8.8
ubuntu
4 дня назад

(In the Linux kernel, the following vulnerability has been resolved: B ...)

CVSS3: 8.8
nvd
4 дня назад

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix the SCO setup context lifetime hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry->data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry->data == conn and entry->data is the wrapper here. Same problem as commit 2f5d635ad590 ("Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks"). Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the de

CVSS3: 8.8
debian
4 дня назад

In the Linux kernel, the following vulnerability has been resolved: B ...

CVSS3: 8.8
github
4 дня назад

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix the SCO setup context lifetime hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry->data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry->data == conn and entry->data is the wrapper here. Same problem as commit 2f5d635ad590 ("Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks"). Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the...

EPSS

Процентиль: 28%
0.00341
Низкий

7.1 High

CVSS3