🛡️ AZL-76767 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2022-50554 affecting package kernel 5.15.200.1-1

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.

Affected software

AZL-76767 is recorded against 1 package.

  • kernel

Timeline and source

Published on 7 October 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-10-07
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-76767?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-76767 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.