Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled HCI_UART_SENDING bit in tx_state means write_work is pending and blocks queueing it again. Currently this bit is not cleared when canceling the work in hci_uart_close(), which blocks future writes when device is reopened later if write_work was pending. Fix by clearing HCI_UART_SENDING when canceling the work. Also make clearing of tx_skb safe by using disable_work_sync + enable_work instead of just cancel_work_sync. hci_uart_flush() purges the proto tx queue so we can cancel the pending write_work there, instead of doing it just in hci_uart_close(). Re-enable and possibly requeue the work after queue flush.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
81c7a3c22a0f2808cf4ae0b4908f59763b23606d to < d52446b3e735cfdbdc2a58342163803bc2e64249affected192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894 to < b9dd39cf1667e378b25a082ca796d495d578c5d3affectedc1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b to < 714d861d35d937f23375a4517569b13917bbbe51affectedc1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b to < 1b0d946d6f08bd39211385bc703a440911b41e46affected78aad93e938f013d9272fe0ee168f27883afa95caffectede2d19969c8d9198ecc3090bcd5312ecd503a3339affectedc85cff648a2bc92322912db5f1727ad05afae7b6affected9d20d48be2c4a071fb015eb09bda2cecd25daf34affected7338031946bd06f6dff149e67b60c4cd083bfea8affected6.12.92 to < 6.12.96affected6.18.34 to < 6.18.39affected5.10.258 to < 5.11affected5.15.209 to < 5.16affected6.1.175 to < 6.2affected6.6.142 to < 6.7affected7.0.11 to < 7.1affected
Linux Linux
Default version status: affected
7.1affected0 to < 7.1unaffected6.12.96 to ≤ 6.12.*unaffected6.18.39 to ≤ 6.18.*unaffected7.1.4 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected