CVE-2024-56714
Last modified
CVE-2024-56714 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.11, < 6.12.7 | — |
| Linux | Linux Kernel | 6.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-56714?
How severe is CVE-2024-56714?
How do I fix CVE-2024-56714?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-56709In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5671Insecure Deserialization in some workflows of the IPS Manage…9.8
- CVE-2024-56710In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56711In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56712In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56713In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56715In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56716In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56717In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56718In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56719In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5672A high privileged remote attacker can execute arbitrary syst…7.2
Are you affected by CVE-2024-56714?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
