CVE-2024-56714 ionic: no double destroy workqueue

Medium 5.5 Published Updated

A double destroy of a workqueue in the ionic driver causes a null pointer dereference, leading to a kernel crash during specific firmware error handling events.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-56714?

CVE-2024-56714 is a medium-severity vulnerability in Linux kernel, published on 29 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2024-56714?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-56714?

Apply the vendor's patch.

Is CVE-2024-56714 being exploited?

There is no known exploitation of CVE-2024-56714 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2024-56714, DEBIAN-CVE-2024-56714, GHSA-hv38-55qj-8p77, UBUNTU-CVE-2024-56714.

Is CVE-2024-56714 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free