Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
f6ec33f6bd3723a8146768106434ef6ab3d9d990| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure
syzbot is reporting NULL pointer dereference at hci_uart_tty_close() [1], for rcu_sync_enter() is called without rcu_sync_init() due to hci_uart_tty_open() ignoring percpu_init_rwsem() failure.
While we are at it, fix that hci_uart_register_device() ignores percpu_init_rwsem() failure and hci_uart_unregister_device() does not call percpu_free_rwsem().
From the CVE record · Linux
The Linux kernel’s Bluetooth HCI UART code can dereference a NULL pointer when initialization of a per-CPU read-write semaphore fails and that failure is ignored. The input does not specify how an attacker could trigger the failure or whether network access, local access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their installations; affected versions were not provided.