CVE-2024-56714
ionic: no double destroy workqueue
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
ionic: no double destroy workqueue
In the Linux kernel, the following vulnerability has been resolved: ionic: no double destroy workqueue There are some FW error handling paths that can cause us to try to destroy the workqueue more than once, so let's be sure we're checking for that. The case where this popped up was in an AER event where the handlers 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 at that time we weren't using a private workqueue. Later we replaced the use of the system workqueue with our own private workqueue but hadn't rerun the AER handler testing since then.
Reserved 2024-12-27 | Published 2024-12-29 | Updated 2025-01-20 | Assigner Linuxgit.kernel.org/...c/13355dd37e22edbcb99c599f783233188740a650
git.kernel.org/...c/746e6ae2e202b062b9deee7bd86d94937997ecd7
Support options
