In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot

Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed
serdev") will cause below regression issue:

BT can't be enabled after below steps:
cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure
if property enable-gpios is not configured within DT|ACPI for QCA6390.

The commit is to fix a use-after-free issue within qca_serdev_shutdown()
by adding condition to avoid the serdev is flushed or wrote after closed
but also introduces this regression issue regarding above steps since the
VSC is not sent to reset controller during warm reboot.

Fixed by sending the VSC to reset controller within qca_serdev_shutdown()
once BT was ever enabled, and the use-after-free issue is also fixed by
this change since the serdev is still opened before it is flushed or wrote.

Verified by the reported machine Dell XPS 13 9310 laptop over below two
kernel commits:
commit e00fc2700a3f ("Bluetooth: btusb: Fix triggering coredump
implementation for QCA") of bluetooth-next tree.
commit b23d98d46d28 ("Bluetooth: btusb: Fix triggering coredump
implementation for QCA") of linus mainline tree.

kernel.org https://git.kernel.org/stable/c/215a26c2404fa34625c725d446967fa328a703eb [No types assigned]

kernel.org https://git.kernel.org/stable/c/4ca6013cd18e58ac1044908c40d4006a92093a11 [No types assigned]

kernel.org https://git.kernel.org/stable/c/88e72239ead9814b886db54fc4ee39ef3c2b8f26 [No types assigned]

kernel.org https://git.kernel.org/stable/c/977b9dc65e14fb80de4763d949c7dec2ecb15b9b [No types assigned]

kernel.org https://git.kernel.org/stable/c/e2d8aa4c763593704ac21e7591aed4f13e32f3b5 [No types assigned]

kernel.org https://git.kernel.org/stable/c/e6e200b264271f62a3fadb51ada9423015ece37b [No types assigned]