Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-57946: virtio-blk: don't keep queue frozen during system suspend

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 12c0ddd6c551c1e438b087f874b4f1223a75f7ea, 4.20, 5.10.233; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.78.1-3.

Low priority for now. Upgrade to Linux Linux 12c0ddd6c551c1e438b087f874b4f1223a75f7ea, 4.20, 5.10.233; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.78.1-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jan 21, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-57946

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.4.289
  • linux linux kernel5.5 and later · before 5.10.233
  • linux linux kernel5.11 and later · before 5.15.176
  • linux linux kernel5.16 and later · before 6.1.123
  • linux linux kernel6.2 and later · before 6.6.69
  • linux linux kernel6.7 and later · before 6.12.8
  • linux linux kernel6.13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2b5128c714d863cd8d259aa9d87bed2d6aa6a5a8, c67ed40b1b4a66e3a13b21bdfbd0151639da5240, 6.8affected
    • b7bfaea8f5ecd290864f5ae4c69859b89832b4dc and later · before d738f3215bb4f88911ff4579780a44960c8e0ca5affected · git
    • 5fe446b245ba61ddc924d7db280bcd987c39357a and later · before 9ca428c6397abaa8c38f5c69133a2299e1efbbf2affected · git
    • 2a52590ac52394540351d8289cc2af0b83cf7d31 and later · before 6dea8e3de59928974bf157dd0499d3958d744ae4affected · git
    • db48acce75d73dfe51c43d56893cce067b73cf08 and later · before 9e323f856cf4963120e0e3892a84ef8bd764a0e4affected · git
    • 8946924ff324853df6b7c525a7467d964dfd11c3 and later · before 12c0ddd6c551c1e438b087f874b4f1223a75f7eaaffected · git
    • 4ce6e2db00de8103a0687fb0f65fd17124a51aaa and later · before 92d5139b91147ab372a17daf5dc27a5b9278e516affected · git
    • 4ce6e2db00de8103a0687fb0f65fd17124a51aaa and later · before 7678abee0867e6b7fb89aa40f6e9f575f755fb37affected · git
    • 5.4.270 and later · before 5.4.289affected · semver
    • 5.10.211 and later · before 5.10.233affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.8-16.12.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-57944Jan 21, 2025 · iio: adc: ti-ads1298: Add NULL check in ads1298_init
    22Monitor
  • ← EarlierCVE-2024-57945Jan 21, 2025 · riscv: mm: Fix the out of bound issue of vmemmap address
    28Monitor
  • Later →CVE-2025-21657Jan 21, 2025 · sched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux12c0ddd6c551c1e438b087f874b4f1223a75f7eaVendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5.10.233Vendor (CNA)
Linux Linux5.15.176Vendor (CNA)
Linux Linux5.4.289Vendor (CNA)
Linux Linux6.1.123Vendor (CNA)
Linux Linux6.6.69Vendor (CNA)
Linux Linux6.8Vendor (CNA)
Linux Linux6dea8e3de59928974bf157dd0499d3958d744ae4Vendor (CNA)
Linux Linux7678abee0867e6b7fb89aa40f6e9f575f755fb37Vendor (CNA)
Linux Linux92d5139b91147ab372a17daf5dc27a5b9278e516Vendor (CNA)
Linux Linux9ca428c6397abaa8c38f5c69133a2299e1efbbf2Vendor (CNA)
Linux Linux9e323f856cf4963120e0e3892a84ef8bd764a0e4Vendor (CNA)
Linux Linuxd738f3215bb4f88911ff4579780a44960c8e0ca5Vendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.78.1-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.78.1-3 on Azure Linux 3.06.6.78.1-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.05.15.176.3-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.05.15.176.3-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.05.15.176.3-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records