![⚡ THN Weekly Recap: Top Cybersecurity Threats, Tools and Tips [30 Dec]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfYK_dlQo9n6UQiuexPS4b1dZ039bN14TXB6AswBkkoRAzzAJg7N3ihBHLhefti8RGcxX6HNI0wVhF8dHLT29WcL2UIUv2n81OsQEbYGKSV6N4aJR-OaK9cV0rWfJWElVsPsjjWvNfb0ZfkRgYfXWIbDBj14YS5VvaBSf7ke5iqzAL2DF7C3IGZRMMwdaf/s1600/recap.png?#)
CVE-2024-56714 - Ionic Double Destroy Workqueue Race Condition
CVE ID : CVE-2024-56714 Published : Dec. 29, 2024, 9:15 a.m. | 15 minutes ago Description : 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. Severity: 0.0 | NA Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE ID : CVE-2024-56714
Published : Dec. 29, 2024, 9:15 a.m. | 15 minutes ago
Description : 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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
Published : Dec. 29, 2024, 9:15 a.m. | 15 minutes ago
Description : 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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
