You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
In the Linux kernel, the following vulnerability has been resolved:
nvme: fix reconnection fail due to reserved tag allocation
We found a issue on production environment while using NVMe over RDMA,
admin_q reconnect failed forever while remote target and network is ok.
After dig into it, we found it may caused by a ABBA deadlock due to tag
allocation. In my case, the tag was hold by a keep alive request
waiting inside admin_q, as we quiesced admin_q while reset ctrl, so the
request maked as idle and will not process before reset success. As
fabric_q shares tagset with admin_q, while reconnect remote target, we
need a tag for connect command, but the only one reserved tag was held
by keep alive command which waiting inside admin_q. As a result, we
failed to reconnect admin_q forever. In order to fix this issue, I
think we should keep two reserved tags for admin queue.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
OR
*cpe:2.3:o:linux:linux_kernel:5.12:rc4:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:-:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc5:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc6:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc7:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.11
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.12.1 up to (excluding) 6.1.83
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.23
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.8 up to (excluding) 6.8.2
*cpe:2.3:o:linux:linux_kernel:5.12:rc8:*:*:*:*:*:*
Removed
CPE Configuration
OR
*cpe:2.3:o:linux:linux_kernel:5.12:rc4:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:-:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc5:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc6:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc7:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.11
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.12.1 up to (excluding) 6.1.83
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.23
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.8 up to (excluding) 6.8.2
*cpe:2.3:o:linux:linux_kernel:5.12:rc8:*:*:*:*:*:*
Initial Analysis by NIST9/19/2025 12:21:58 PM
Action
Type
Old Value
New Value
Added
CVSS V3.1
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Added
CWE
CWE-667
Added
CPE Configuration
OR
*cpe:2.3:o:linux:linux_kernel:5.12:rc4:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:-:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc5:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc6:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:5.12:rc7:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.11
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.12.1 up to (excluding) 6.1.83
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.23
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.8 up to (excluding) 6.8.2
*cpe:2.3:o:linux:linux_kernel:5.12:rc8:*:*:*:*:*:*
New CVE Received from kernel.org5/17/2024 9:15:58 AM
Action
Type
Old Value
New Value
Added
Description
In the Linux kernel, the following vulnerability has been resolved:
nvme: fix reconnection fail due to reserved tag allocation
We found a issue on production environment while using NVMe over RDMA,
admin_q reconnect failed forever while remote target and network is ok.
After dig into it, we found it may caused by a ABBA deadlock due to tag
allocation. In my case, the tag was hold by a keep alive request
waiting inside admin_q, as we quiesced admin_q while reset ctrl, so the
request maked as idle and will not process before reset success. As
fabric_q shares tagset with admin_q, while reconnect remote target, we
need a tag for connect command, but the only one reserved tag was held
by keep alive command which waiting inside admin_q. As a result, we
failed to reconnect admin_q forever. In order to fix this issue, I
think we should keep two reserved tags for admin queue.