CVE-2024-57946
Last modified
CVE-2024-57946 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don't keep queue frozen during system suspend Commit 4ce6e2db00de ("virtio-blk: Ensure no requests in virtqueues before deleting vqs.") replaces queue quiesce with queue freeze in virtio-blk's PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer's queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if the queue is frozen in current context. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don't keep queue frozen during system suspend Commit 4ce6e2db00de ("virtio-blk: Ensure no requests in virtqueues before deleting vqs.") replaces queue quiesce with queue freeze in virtio-blk's PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer's queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if the queue is frozen in current context. There are all kinds of ->suspend() called in suspend context, so keeping queue frozen in the whole suspend context isn't one good idea. And Marek reported lockdep warning[1] caused by virtio-blk's freeze queue in virtblk_freeze(). [1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/ Given the motivation is to drain in-flight IOs, it can be done by calling freeze & unfreeze, meantime restore to previous behavior by keeping queue quiesced during suspend.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | < 5.4.289 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.233 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.176 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.123 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.69 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.8 | — |
| Linux | Linux Kernel | 6.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-57946?
How severe is CVE-2024-57946?
How do I fix CVE-2024-57946?
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-57940In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57941In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57942In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57943In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-57944In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57945In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-57947In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57948In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57949In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5795A Denial of Service vulnerability was identified in GitHub E…6.5
- CVE-2024-57950In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57951In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2024-57946?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
