In the Linux kernel, the following vulnerability has been resolved:ionic: no double destroy workqueueThere are some FW error handling paths that can cause us totry to destroy the workqueue more than once, so let's be surewe're checking for that.The case where this popped up was in an AER event where thehandlers got called in such a way that ionic_reset_prepare()and thus ionic_dev_teardown() got called twice in a row.The second time through the workqueue was already destroyed,and destroy_workqueue() choked on the bad wq pointer.We didn't hit this in AER handler testing before because atthat time we weren't using a private workqueue. Later wereplaced the use of the system workqueue with our own privateworkqueue but hadn't rerun the AER handler testing since then.
