LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50554: blk-mq: avoid double ->queue_rq() because of early timeout

In the Linux kernel, the following vulnerability has been resolved: blk-mq: avoid double ->queue_rq() because of early timeout David Jeffery found one double ->queue_rq() issue, so far it can be triggered in VM use case because of long vmexit latency or preempt latency of vCPU pthread or long page fault in vCPU pthread, then block IO req could be timed out before queuing the request to hardware but after calling blk_mq_start_request() during ->queue_rq(), then timeout handler may handle it by requeue, then double ->queue_rq() is caused, and kernel panic. So far, it is driver's responsibility to cover the race between timeout and completion, so it seems supposed to be solved in driver in theory, given driver has enough knowledge. But it is really one common problem, lots of driver could have similar issue, and could be hard to fix all affected drivers, even it isn't easy for driver to handle the race. So David suggests this patch by draining in-progress ->queue_rq() for solving this issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a kernel panic when block I/O request handling races with an early timeout. The public record describes VM-related latency conditions as a known trigger. Business impact is primarily availability: affected systems may crash rather than leak data or enable direct takeover, based on the provided evidence.

Executive priority

Treat as a reliability patching item for Linux fleets, with higher priority for virtualized infrastructure and availability-sensitive workloads. No source evidence supports emergency active-exploitation response.

Technical view

The flaw is in blk-mq request handling. After blk_mq_start_request() during ->queue_rq(), a request can time out before hardware queueing completes. The timeout path may requeue it, causing double ->queue_rq() and a kernel panic. The fix direction described is draining in-progress ->queue_rq() work.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions, especially virtualized workloads with long vmexit, vCPU preemption, or page fault latency. The affected version data is incomplete and should be validated against distribution kernel advisories.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. It describes a trigger condition observed in VM use cases, but provides no evidence of public weaponization or remote exploitability.

Researcher notes

The CVE record lacks CVSS, CWE, and complete affected range precision. The core condition is a blk-mq timeout/requeue race that can double-submit ->queue_rq(). Research should focus on vendor kernel mapping and crash correlation, not exploit assumptions.

Mitigation direction

  • Inventory Linux kernel versions across hosts and guest VMs.
  • Check Linux distribution advisories for CVE-2022-50554 coverage.
  • Prioritize kernel updates containing the referenced stable blk-mq fixes.
  • Monitor systems for kernel panics tied to block I/O timeouts.
  • Avoid assuming driver-specific workarounds unless vendor guidance supports them.

Validation and detection

  • Confirm whether deployed kernels match affected versions or vendor backports.
  • Review kernel changelogs for the referenced blk-mq stable commits.
  • Check crash logs for block I/O timeout and queue_rq panic patterns.
  • Validate patched kernels in VM workloads with representative I/O latency.
  • Track vendor advisories because source version ranges are not fully precise.
Prepared
Confidence
medium
Sources
5

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.

cve · low confidence lookup

CVE-2022-50554 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux12f5b93145450c750f315657ef239a314811aeeb, 12f5b93145450c750f315657ef239a314811aeeb, 12f5b93145450c750f315657ef239a314811aeebunaffected
LinuxLinux4.18, 0, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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