System hang via frozen virtio-blk suspend queue
Published Jan 21, 2025 · Updated May 23, 2026
Improper locking in affected Linux kernel versions allows local users to hang the system during system suspend operations. In virtblk_freeze(), the virtio-blk power-management callback leaves the request queue frozen throughout suspend, so reentrant bio_queue_enter() waits on the freeze held by the same context. Reachability requires a virtio block device and a suspend callback that enters block I/O; the resulting deadlock interrupts system operation without reported data disclosure or modification.
Summary
What happened
Improper locking in affected Linux kernel versions allows local users to hang the system during system suspend operations. In virtblk_freeze(), the virtio-blk power-management callback leaves the request queue frozen throughout suspend, so reentrant bio_queue_enter() waits on the freeze held by the same context. Reachability requires a virtio block device and a suspend callback that enters block I/O; the resulting deadlock interrupts system operation without reported data disclosure or modification.
The record
- CVE
- CVE-2024-57946
- Published
- Jan 21, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2a52590ac52394540351d8289cc2af0b83cf7d31 <6dea8e3de59928974bf157dd0499d3958d744ae4
- Affected versionversion=2b5128c714d863cd8d259aa9d87bed2d6aa6a5a8
- Affected versionversion=4.19.308 <4.20
- Affected versionversion=4ce6e2db00de8103a0687fb0f65fd17124a51aaa <7678abee0867e6b7fb89aa40f6e9f575f755fb37
- Affected versionversion=4ce6e2db00de8103a0687fb0f65fd17124a51aaa <92d5139b91147ab372a17daf5dc27a5b9278e516
- Affected versionversion=5.10.211 <5.10.233
- Affected versionversion=5.15.150 <5.15.176
- Affected versionversion=5.4.270 <5.4.289
- Affected versionversion=5fe446b245ba61ddc924d7db280bcd987c39357a <9ca428c6397abaa8c38f5c69133a2299e1efbbf2
- Affected versionversion=6.1.80 <6.1.123
- Affected versionversion=6.6.19 <6.6.69
- Affected versionversion=6.7.7 <6.8
- Affected versionversion=6.8
- Affected versionversion=8946924ff324853df6b7c525a7467d964dfd11c3 <12c0ddd6c551c1e438b087f874b4f1223a75f7ea
- Affected versionversion=b7bfaea8f5ecd290864f5ae4c69859b89832b4dc <d738f3215bb4f88911ff4579780a44960c8e0ca5
- Affected versionversion=c67ed40b1b4a66e3a13b21bdfbd0151639da5240
- Affected versionversion=db48acce75d73dfe51c43d56893cce067b73cf08 <9e323f856cf4963120e0e3892a84ef8bd764a0e4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo