Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.249, 5.15.199, 6.1.162, 6.6.123, 6.12.69, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling hci_uart_register_dev(), which calls proto->open() to initialize hu->priv. However, if a TTY write wakeup occurs during this window, hci_uart_tx_wakeup() may schedule write_work before hu->priv is initialized, leading to a NULL pointer dereference in hci_uart_write_work() when proto->dequeue() accesses hu->priv. The race condition is: CPU0 CPU1 ---- ---- hci_uart_set_proto() set_bit(HCI_UART_PROTO_INIT) hci_uart_register_dev() tty write wakeup hci_uart_tty_wakeup() hci_uart_tx_wakeup() schedule_work(&hu->write_work) proto->open(hu) // initializes hu->priv hci_uart_write_work() hci_uart_dequeue() proto->dequeue(hu) // accesses hu->priv (NULL!) Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto->open() succeeds, ensuring hu->priv is initialized before any work can be scheduled.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From a40f94f7caa8d3421b64f63ac31bc0f24c890f39 · fixed in b0a900939e7e4866d9b90e9112514b72c451e873; From 9e5a0f5777162e503400c70c6ed25fbbe2d38799 · fixed in ccc683f597ceb28deb966427ae948e5ac739a909; From 80f14e9de6a43a0bd8194cad1003a3e6dcbc3984 · fixed in 937a573423ce5a96fdb1fd425dc6b8d8d4ab5779; From 02e1bcdfdf769974e7e9fa285e295cd9852e2a38 · fixed in 186d147cf7689ba1f9b3ddb753ab634a84940cc9; From 281782d2c6730241e300d630bb9f200d831ede71 · fixed in 53e54cb31e667fca05b1808b990eac0807d1dab0; From 5df5dafc171b90d0b8d51547a82657cd5a1986c7 · fixed in 03e8c90c62233382042b7bd0fa8b8900552fdb62; From 5df5dafc171b90d0b8d51547a82657cd5a1986c7 · fixed in 0c3cd7a0b862c37acbee6d9502107146cc944398; From 5.10.237 · fixed in 5.10.249; From 5.15.181 · fixed in 5.15.199; From 6.1.135 · fixed in 6.1.162; From 6.6.88 · fixed in 6.6.123; From 6.12.24 · fixed in 6.12.69; From 5.4.293 · fixed in 5.5; From 6.13.12 · fixed in 6.14; From 6.14.3 · fixed in 6.15
- Linux Linux
6.15
- KernelLinux
fixed in 5.10.249; From 5.11.0 · fixed in 5.15.199; From 5.16.0 · fixed in 6.1.162; From 6.2.0 · fixed in 6.6.123; From 6.7.0 · fixed in 6.12.69; From 6.13.0 · fixed in 6.18.9
References 7
git.kernel.org
- stable/c/b0a900939e7e4866d9b90e9112514b72c451e873
- stable/c/ccc683f597ceb28deb966427ae948e5ac739a909
- stable/c/937a573423ce5a96fdb1fd425dc6b8d8d4ab5779
- stable/c/186d147cf7689ba1f9b3ddb753ab634a84940cc9
- stable/c/53e54cb31e667fca05b1808b990eac0807d1dab0
- stable/c/03e8c90c62233382042b7bd0fa8b8900552fdb62
- stable/c/0c3cd7a0b862c37acbee6d9502107146cc944398