CVE-2024-56714: 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 ionicresetprepare() and thus ionicdevteardown() got called twice in a row. The second time through the workqueue was already destroyed, and destroyworkqueue() 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.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56714?
CVE-2024-56714 has been classified as a medium severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-56714?
To fix CVE-2024-56714, update your Linux kernel to the latest patched version provided by your distribution.
What systems are affected by CVE-2024-56714?
CVE-2024-56714 affects various versions of the Linux kernel that utilize the ionic driver.
What does CVE-2024-56714 exploit?
CVE-2024-56714 exploits a flaw in error handling that can lead to an attempt to destroy a workqueue more than once.
Is CVE-2024-56714 being actively exploited?
As of now, there are no reported active exploits for CVE-2024-56714, but it is still recommended to apply patches promptly.