LiveActive security incident?Get immediate response
CVE Record

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

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.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make affected systems hang during power management suspend because virtio-blk may leave a block queue frozen too long. The direct business impact is availability: workloads could stall or require recovery if suspend paths are reached on vulnerable systems.

Executive priority

Treat as a moderate availability risk. It is not described as data theft or remote compromise, but kernel-level hangs can disrupt services, especially in virtualized environments. Patch through normal kernel maintenance with priority for exposed virtio-blk systems.

Technical view

The flaw is in virtio-blk power-management callbacks. A prior change used queue freeze to drain in-flight I/O before suspend, but keeping the queue frozen across suspend can deadlock callers entering bio_queue_enter(). The fix restores quiesced suspend behavior while briefly freezing and unfreezing to drain I/O.

Likely exposure

Exposure is most relevant to Linux systems using virtio-blk block devices on affected kernel versions or downstream packages. The provided data names Linux as the affected product and lists stable kernel fixes and Debian LTS advisories.

Exploitation context

The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact. The source bundle does not show KEV listing or cited active exploitation evidence.

Researcher notes

Evidence is specific to Linux virtio-blk suspend behavior and CWE-667 locking. The bundle provides stable commit references but not complete downstream package mapping for all distributions. Avoid assuming exploit availability; validation should focus on kernel lineage, driver presence, and vendor advisory status.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize virtualized Linux systems using virtio-blk storage.
  • Review Debian LTS advisories if running affected Debian packages.
  • Check your distribution advisory before relying on workarounds.
  • Schedule reboot or live-patching per standard kernel update process.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Confirm whether virtio-blk devices are present on those systems.
  • Verify the applicable stable fix is included in the running kernel.
  • Check Debian advisory coverage for Debian LTS hosts.
  • Regression test suspend and resume where that path is operationally used.
Prepared
Confidence
high
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57946 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-57946Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb7bfaea8f5ecd290864f5ae4c69859b89832b4dc, 5fe446b245ba61ddc924d7db280bcd987c39357a, 2a52590ac52394540351d8289cc2af0b83cf7d31, db48acce75d73dfe51c43d56893cce067b73cf08, 8946924ff324853df6b7c525a7467d964dfd11c3, 4ce6e2db00de8103a0687fb0f65fd17124a51aaa, 4ce6e2db00de8103a0687fb0f65fd17124a51aaa, 2b5128c714d863cd8d259aa9d87bed2d6aa6a5a8, c67ed40b1b4a66e3a13b21bdfbd0151639da5240, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 4.19.308, 6.7.7unaffected
LinuxLinux6.8, 0, 5.4.289, 5.10.233, 5.15.176, 6.1.123, 6.6.69, 6.12.8, 6.13affected
Weakness

CWE details

CWE-667

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs