CVE-2026-64405

CVE CVE-2026-64405EUVD EUVD-2026-48949Veröffentlicht 2026-07-25T08:50:47.000Z

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() hci_abort_conn() read hci_skb_event(hdev->sent_cmd) when a connection was pending, but hdev->sent_cmd can be NULL while req_status is still HCI_REQ_PEND, leading to a NULL pointer dereference and a general protection fault from the hci_rx_work() receive path. Instead of inspecting hdev->sent_cmd, track the in-flight create connection command with a new per-connection HCI_CONN_CREATE flag and route all cancellation through hci_cancel_connect_sync(), which dispatches to a dedicated per-type cancel function. The create command is in exactly one of two states: still queued, or in flight. The cancel function holds cmd_sync_work_lock across the whole decision: the worker takes this lock to dequeue every entry, so while it is held a queued command cannot start running and an in-flight command cannot complete and let the next command become pending. This keeps the flag test and hci_cmd_sync_cancel() atomic with respect to the worker, so a queued command is simply dequeued, and an in-flight command owned by this connection is cancelled without the risk of cancelling an unrelated command that became pending in the meantime. CIS uses the same flag mechanism via HCI_CONN_CREATE_CIS but cannot be dequeued per-connection. hci_acl_create_conn_sync() and hci_le_create_conn_sync() clear HCI_CONN_CREATE after the create command completes, but the command status handler can free conn via hci_conn_del() (for example when the controller rejects the connection) while the worker is still blocked on the connection complete event. Hold a reference on conn across the create command so the flag can be cleared without a use-after-free.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux patch: 6.18.39; 4ab81f16c68a602b2b69e333ae08d8748a9398de; 6083089ab00631617f9eac678df3ab050a9d837a <903227b6168bb99fd57d4e3c9c1b5014986198e0; a13f316e90fdb1fb6df6582e845aa9b3270f3581 <61701912c58a05f6a043f097cc177a964abef348; patch: 7.1.4; a13f316e90fdb1fb6df6582e845aa9b3270f3581 <70c397b62ee015e19b3924d9da741c8dda017819; patch: 0; 6.6; e4511a67fcdba9729d1c7cfc6d2e645c765ce801; a13f316e90fdb1fb6df6582e845aa9b3270f3581 <12917f591cea1af36087dba5b9ec888652f0b42a; patch: 6.12.97; a13f316e90fdb1fb6df6582e845aa9b3270f3581 <b42cb640a0493d16b61ddd267420274be15efdc1; a13f316e90fdb1fb6df6582e845aa9b3270f3581 <83b22d7f7c384564fa42c3cf19bec715c693d7a2; patch: 6.6.145; 6.4.16 <6.5; patch: 6.1.118; 6.1.83 <6.1.118; 6.5.3 <6.6; patch: 7.2-rc3

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.