---
id: CVE-2024-49569
title: 'nvme-rdma: unquiesce admin_q before destroy it'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvme-rdma: unquiesce admin_q before destroy it

  Kernel will hang on destroy admin_q while we create ctrl failed, such
  as following calltrace:

  PID: 23644    TASK: ff2d5…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 <
    53bdbe5dc80b5887af51d62bf44e50f56972db5f
  - >-
    Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 <
    427036030f4d796533dcadba9b845896cb6c10a7
  - >-
    Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 <
    05b436f3cf65c957eff86c5ea5ddfa2604b32c63
  - >-
    Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 <
    5858b687559809f05393af745cbadf06dee61295
  - Linux a9ea34d2717a8c8892d3c5677329de9485e325ac
  - Linux 7da81eaf8710130a9e63d7429627183be5a93787
  - Linux caed0b3851a4f52afd1ef77a27b30410fe7b68c7
  - Linux >= 5.4.103 < 5.5
  - Linux >= 5.10.21 < 5.11
  - Linux >= 5.11.4 < 5.12
  - Linux 5.12
published: '2025-01-11'
updated: '2026-10-30'
sourceUpdated: '2026-10-30T12:19:31.857Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2024-49569'
references:
  - url: 'https://git.kernel.org/stable/c/53bdbe5dc80b5887af51d62bf44e50f56972db5f'
  - url: 'https://git.kernel.org/stable/c/427036030f4d796533dcadba9b845896cb6c10a7'
  - url: 'https://git.kernel.org/stable/c/05b436f3cf65c957eff86c5ea5ddfa2604b32c63'
  - url: 'https://git.kernel.org/stable/c/5858b687559809f05393af745cbadf06dee61295'
tags:
  - cve.org
epss: 0.00842
epssPercentile: 0.58177
ingestedAt: '2026-11-03T13:45:42.697Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

nvme-rdma: unquiesce admin_q before destroy it

Kernel will hang on destroy admin_q while we create ctrl failed, such
as following calltrace:

PID: 23644    TASK: ff2d52b40f439fc0  CPU: 2    COMMAND: "nvme"
 #0 [ff61d23de260fb78] __schedule at ffffffff8323bc15
 #1 [ff61d23de260fc08] schedule at ffffffff8323c014
 #2 [ff61d23de260fc28] blk_mq_freeze_queue_wait at ffffffff82a3dba1
 #3 [ff61d23de260fc78] blk_freeze_queue at ffffffff82a4113a
 #4 [ff61d23de260fc90] blk_cleanup_queue at ffffffff82a33006
 #5 [ff61d23de260fcb0] nvme_rdma_destroy_admin_queue at ffffffffc12686ce
 #6 [ff61d23de260fcc8] nvme_rdma_setup_ctrl at ffffffffc1268ced
 #7 [ff61d23de260fd28] nvme_rdma_create_ctrl at ffffffffc126919b
 #8 [ff61d23de260fd68] nvmf_dev_write at ffffffffc024f362
 #9 [ff61d23de260fe38] vfs_write at ffffffff827d5f25
    RIP: 00007fda7891d574  RSP: 00007ffe2ef06958  RFLAGS: 00000202
    RAX: ffffffffffffffda  RBX: 000055e8122a4d90  RCX: 00007fda7891d574
    RDX: 000000000000012b  RSI: 000055e8122a4d90  RDI: 0000000000000004
    RBP: 00007ffe2ef079c0   R8: 000000000000012b   R9: 000055e8122a4d90
    R10: 0000000000000000  R11: 0000000000000202  R12: 0000000000000004
    R13: 000055e8122923c0  R14: 000000000000012b  R15: 00007fda78a54500
    ORIG_RAX: 0000000000000001  CS: 0033  SS: 002b

This due to we have quiesced admi_q before cancel requests, but forgot
to unquiesce before destroy it, as a result we fail to drain the
pending requests, and hang on blk_mq_freeze_queue_wait() forever. Here
try to reuse nvme_rdma_teardown_admin_queue() to fix this issue and
simplify the code.

## Affected

- `Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 < 53bdbe5dc80b5887af51d62bf44e50f56972db5f`
- `Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 < 427036030f4d796533dcadba9b845896cb6c10a7`
- `Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 < 05b436f3cf65c957eff86c5ea5ddfa2604b32c63`
- `Linux >= 958dc1d32c80566f58d18f05ef1f05bd32d172c1 < 5858b687559809f05393af745cbadf06dee61295`
- `Linux a9ea34d2717a8c8892d3c5677329de9485e325ac`
- `Linux 7da81eaf8710130a9e63d7429627183be5a93787`
- `Linux caed0b3851a4f52afd1ef77a27b30410fe7b68c7`
- `Linux >= 5.4.103 < 5.5`
- `Linux >= 5.10.21 < 5.11`
- `Linux >= 5.11.4 < 5.12`
- `Linux 5.12`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.