Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu->proto->close(hu) and setting hu->hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu->proto->close() and setting hu->hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed. This allows the protocol-specific recv functions to remove the "HCI_UART_REGISTERED" guard without risking a null pointer dereference if hci_register_dev() fails.

Affected products

Linux
  • <f4b69c35813c432973d340d3600c01de106ed474
  • =<6.18.*
  • <5.15.209
  • =<7.0.*
  • <6.14
  • <ebb39b2d81731b83ee71a1ba6dd0291a57b5ac07
  • <5.10.258
  • =<6.1.*
  • <a673cf6c4ac702cb79ac1f4d7fc4de763a6a3e40
  • ==1dcf08fcff5ca529de6dc0395091f28854f4e54a
  • <6.15
  • <ed4033fb85ccaaf6c3983be3c7b037e48253d232
  • <194f029a4d7f739e44ebc1f473120187b4de5104
  • <6.1.175
  • ==8e5aff600539e5faea294d9612cca50220e602b8
  • <3daa5818e473ed60eb69d8b5c71b651909d28c5a
  • <5.5
  • <6.6.141
  • ==db7509fa110dd9b11134b75894677f30353b2c51
  • <68d39ea5e0adc9ecaea1ce8abd842ec972eb8718
  • =<5.15.*
  • ==6.15
  • =<*
  • <6.12.91
  • <6.15
  • <356dee1bcac4d0d9152390561fa63331ebff211b
  • =<6.12.*
  • =<5.10.*
  • =<6.6.*