CVE-2026-46275

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths Vulnerabilities leading to Use-After-Free (UAF) and Null Pointer Dereference (NPD) conditions were observed in the lifecycle management of hci_uart. The primary issue arises because the workqueues (init_ready and write_work) are only flushed/cancelled if the HCI_UART_PROTO_READY flag is set during TTY close. If a hangup occurs before setup completes, hci_uart_tty_close() skips the teardown of these workqueues and proceeds to free the `hu` struct. When the scheduled work executes later, it blindly dereferences the freed `hu` struct. Furthermore, several data races and UAFs were identified in the teardown sequence: 1. Calling hci_uart_flush() from hci_uart_close() without effectively disabling write_work causes a race condition where both can concurrently double-free hu->tx_skb. This happens because protocol timers can concurrently invoke hci_uart_tx_wakeup() and requeue write_work. 2. Calling hci_free_dev(hdev) before hu->proto->close(hu) causes a UAF when vendor specific protocol close callbacks dereference hu->hdev. 3. In the initialization error paths, failing to take the proto_lock write lock before clearing PROTO_READY leads to races with active readers. Additionally, hci_uart_tty_receive() accesses hu->hdev outside the read lock, leading to UAFs if the initialization error path frees hdev concurrently. Fix these synchronization and lifecycle issues by: 1. Re-ordering hci_uart_tty_close() to clear HCI_UART_PROTO_READY first, followed immediately by a cancel_work_sync(&hu->write_work). Clearing the flag locks out concurrent protocol timers from successfully invoking hci_uart_tx_wakeup(), effectively rendering the cancellation permanent and preventing the tx_skb double-free. 2. Note: Clearing PROTO_READY early causes hci_uart_close() to skip hu->proto->flush(). This is perfectly safe in the tty_close path because hu->proto->close() executes shortly after, which intrinsically purges all protocol SKB queues and tears down the state. 3. Relocating hu->proto->close(hu) strictly prior to hci_free_dev(hdev) across all close and error paths to prevent vendor-level UAFs. 4. Moving the hdev->stat.byte_rx increment in hci_uart_tty_receive() inside the proto_lock read-side critical section to safely synchronize with device unregistration. 5. Adding cancel_work_sync(&hu->write_work) to hci_uart_close() to safely flush the workqueue before hci_uart_flush() is invoked via the HCI core. 6. Utilizing cancel_work_sync() instead of disable_work_sync() across all paths to prevent permanently breaking user-space retry capabilities.

CVSS Metrics

• v4.0•HIGH•Score: 7.1CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
• v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.19%• Percentile: 9%

Techniques & Countermeasures

• CWE-362•Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Systems

• debian•linux

  < 5.10.259-1 | < 6.1.176-1 | < 6.12.94-1 | < 7.0.12-1

• debian•linux-6.1

  < 6.1.176-1~deb11u1

• ubuntu•linux

  all | all | < 5.15.0-186.196 | < 6.8.0-139.139 | all | < 7.0.0-28.28

• ubuntu•linux-allwinner-5.19

  all

• ubuntu•linux-aws

  all | < 5.15.0-1112.119 | all | all | < 7.0.0-1009.9

• ubuntu•linux-aws-5.0

  all

• ubuntu•linux-aws-5.11

  all

• ubuntu•linux-aws-5.13

  all

• ubuntu•linux-aws-5.15

  < 5.15.0-1112.119~20.04.1

• ubuntu•linux-aws-5.19

  all

• ubuntu•linux-aws-5.3

  all

• ubuntu•linux-aws-5.4

  all

• ubuntu•linux-aws-5.8

  all

• ubuntu•linux-aws-6.14

  all

• ubuntu•linux-aws-6.17

  all

• ubuntu•linux-aws-6.2

  all

• ubuntu•linux-aws-6.5

  all

• ubuntu•linux-aws-6.8

  all

• ubuntu•linux-aws-fips

  all | < 5.15.0-1112.119+fips1

• ubuntu•linux-aws-hwe

  all

• ubuntu•linux-azure

  all | all | all | < 5.15.0-1117.126 | < 6.8.0-1067.75 | all | < 7.0.0-1010.10

• ubuntu•linux-azure-4.15

  all

• ubuntu•linux-azure-5.11

  all

• ubuntu•linux-azure-5.13

  all

• ubuntu•linux-azure-5.15

  < 5.15.0-1117.126~20.04.1

• ubuntu•linux-azure-5.19

  all

• ubuntu•linux-azure-5.3

  all

• ubuntu•linux-azure-5.4

  all

• ubuntu•linux-azure-5.8

  all

• ubuntu•linux-azure-6.11

  all

• ubuntu•linux-azure-6.14

  all

• ubuntu•linux-azure-6.17

  all

• ubuntu•linux-azure-6.2

  all

• ubuntu•linux-azure-6.5

  all

• ubuntu•linux-azure-6.8

  all

• ubuntu•linux-azure-7.0

  all

• ubuntu•linux-azure-edge

  all

• ubuntu•linux-azure-fde

  all | < 5.15.0-1117.126 | all | all | < 7.0.0-1009.9

• ubuntu•linux-azure-fde-5.15

  < 5.15.0-1117.126~20.04.2

• ubuntu•linux-azure-fde-5.19

  all

• ubuntu•linux-azure-fde-6.14

  all

• ubuntu•linux-azure-fde-6.17

  all

• ubuntu•linux-azure-fde-6.2

  all

• ubuntu•linux-azure-fde-6.8

  all

• ubuntu•linux-azure-fips

  all | < 5.15.0-1117.126+fips1 | < 6.8.0-1067.75+fips1

• ubuntu•linux-azure-nvidia

  all

• ubuntu•linux-azure-nvidia-6.14

  all

• ubuntu•linux-bluefield

  all | all | < 5.15.0-1096.98 | < 6.8.0-1030.35

• ubuntu•linux-fips

  all | < 5.15.0-186.196+fips1 | < 6.8.0-139.139+fips1

• ubuntu•linux-gcp

  all | all | all | < 5.15.0-1112.122 | < 6.8.0-1067.75 | all | < 7.0.0-1008.8

Showing first 50 affected entries in server-rendered view.

References (38)

• https://git.kernel.org/stable/c/78aad93e938f013d9272fe0ee168f27883afa95c
• https://git.kernel.org/stable/c/e2d19969c8d9198ecc3090bcd5312ecd503a3339
• https://git.kernel.org/stable/c/c85cff648a2bc92322912db5f1727ad05afae7b6
• https://git.kernel.org/stable/c/9d20d48be2c4a071fb015eb09bda2cecd25daf34
• https://git.kernel.org/stable/c/81c7a3c22a0f2808cf4ae0b4908f59763b23606d
• https://git.kernel.org/stable/c/192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894
• https://git.kernel.org/stable/c/7338031946bd06f6dff149e67b60c4cd083bfea8
• https://git.kernel.org/stable/c/c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b
• https://ubuntu.com/security/CVE-2026-46275
• https://www.cve.org/CVERecord?id=CVE-2026-46275
• https://git.kernel.org/linus/c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b
• https://ubuntu.com/security/notices/USN-8566-1
• https://ubuntu.com/security/notices/USN-8568-1
• https://ubuntu.com/security/notices/USN-8569-1
• https://ubuntu.com/security/notices/USN-8575-1
• https://ubuntu.com/security/notices/USN-8576-1
• https://ubuntu.com/security/notices/USN-8593-1
• https://ubuntu.com/security/notices/USN-8575-2
• https://ubuntu.com/security/notices/USN-8576-2
• https://ubuntu.com/security/notices/USN-8597-1
• https://ubuntu.com/security/notices/USN-8603-1
• https://ubuntu.com/security/notices/USN-8575-3
• https://ubuntu.com/security/notices/USN-8610-1
• https://ubuntu.com/security/notices/USN-8618-1
• https://ubuntu.com/security/notices/USN-8620-1
• https://ubuntu.com/security/notices/USN-8620-2
• https://ubuntu.com/security/notices/USN-8620-3
• https://ubuntu.com/security/notices/USN-8620-4
• https://security-tracker.debian.org/tracker/CVE-2026-46275
• https://ubuntu.com/security/notices/USN-8663-1
• https://ubuntu.com/security/notices/USN-8664-1
• https://ubuntu.com/security/notices/USN-8668-1
• https://ubuntu.com/security/notices/USN-8728-1
• https://ubuntu.com/security/notices/USN-8729-1
• https://ubuntu.com/security/notices/USN-8761-1
• https://ubuntu.com/security/notices/USN-8729-2
• https://ubuntu.com/security/notices/USN-8761-2
• https://ubuntu.com/security/notices/USN-8781-1