CVE-2024-56714: ionic: no double destroy workqueue

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-12-29 · updated 2026-06-17

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.

Affected products

Linux kernel: from 6.11 before 6.12.7; 6.13-rc1, 6.13-rc2, 6.13-rc3 — fixed in 6.12.7

How to fix

Upgrade to a fixed version: Linux kernel 6.12.7. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-56714 or the next vulnerability affects your stack