CVE-2026-45855
Awaiting Analysis Awaiting Analysis - Queue
ATA Command Starvation in Linux Kernel

Publication date: 2026-05-27

Last updated on: 2026-05-27

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ata: libata-scsi: avoid Non-NCQ command starvation When a non-NCQ command is issued while NCQ commands are being executed, ata_scsi_qc_issue() indicates to the SCSI layer that the command issuing should be deferred by returning SCSI_MLQUEUE_XXX_BUSY. This command deferring is correct and as mandated by the ACS specifications since NCQ and non-NCQ commands cannot be mixed. However, in the case of a host adapter using multiple submission queues, when the target device is under a constant load of NCQ commands, there are no guarantees that requeueing the non-NCQ command will be executed later and it may be deferred again repeatedly as other submission queues can constantly issue NCQ commands from different CPUs ahead of the non-NCQ command. This can lead to very long delays for the execution of non-NCQ commands, and even complete starvation for these commands in the worst case scenario. Since the block layer and the SCSI layer do not distinguish between queueable (NCQ) and non queueable (non-NCQ) commands, libata-scsi SAT implementation must ensure forward progress for non-NCQ commands in the presence of NCQ command traffic. This is similar to what SAS HBAs with a hardware/firmware based SAT implementation do. Implement such forward progress guarantee by limiting requeueing of non-NCQ commands from ata_scsi_qc_issue(): when a non-NCQ command is received and NCQ commands are in-flight, do not force a requeue of the non-NCQ command by returning SCSI_MLQUEUE_XXX_BUSY and instead return 0 to indicate that the command was accepted but hold on to the qc using the new deferred_qc field of struct ata_port. This deferred qc will be issued using the work item deferred_qc_work running the function ata_scsi_deferred_qc_work() once all in-flight commands complete, which is checked with the port qc_defer() callback return value indicating that no further delay is necessary. This check is done using the helper function ata_scsi_schedule_deferred_qc() which is called from ata_scsi_qc_complete(). This thus excludes this mechanism from all internal non-NCQ commands issued by ATA EH. When a port deferred_qc is non NULL, that is, the port has a command waiting for the device queue to drain, the issuing of all incoming commands (both NCQ and non-NCQ) is deferred using the regular busy mechanism. This simplifies the code and also avoids potential denial of service problems if a user issues too many non-NCQ commands. Finally, whenever ata EH is scheduled, regardless of the reason, a deferred qc is always requeued so that it can be retried once EH completes. This is done by calling the function ata_scsi_requeue_deferred_qc() from ata_eh_set_pending(). This avoids the need for any special processing for the deferred qc in case of NCQ error, link or device reset, or device timeout.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-05-27
Generated
2026-06-16
AI Q&A
2026-05-28
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Mitigation Strategies

The vulnerability is resolved in the Linux kernel by implementing a forward progress guarantee for non-NCQ commands in the presence of NCQ command traffic. Immediate mitigation involves updating the Linux kernel to a version that includes this fix.

This fix avoids starvation of non-NCQ commands by limiting their requeueing and ensuring they are eventually issued even under heavy NCQ load.

Executive Summary

This vulnerability exists in the Linux kernel's ATA SCSI subsystem where non-NCQ (Non-Queued Command) commands can be starved when multiple NCQ (Native Command Queuing) commands are continuously issued. Normally, when a non-NCQ command is issued while NCQ commands are in progress, the system defers the non-NCQ command to comply with ACS specifications, which prohibit mixing NCQ and non-NCQ commands simultaneously.

However, on host adapters using multiple submission queues, if the device is constantly busy with NCQ commands, the non-NCQ commands may be repeatedly deferred and never executed, causing very long delays or complete starvation of these commands.

The fix ensures forward progress for non-NCQ commands by limiting their requeueing. Instead of deferring non-NCQ commands repeatedly, the system accepts them and holds them until all in-flight NCQ commands complete, then issues the deferred non-NCQ commands. This mechanism prevents starvation and ensures non-NCQ commands are eventually processed.

Impact Analysis

This vulnerability can cause significant delays or complete starvation of non-NCQ commands on affected Linux systems using certain host adapters with multiple submission queues. This means that some commands may never be executed or experience very long wait times.

Such delays can degrade system performance, potentially causing applications or processes that rely on timely execution of these commands to hang, slow down, or fail. In worst-case scenarios, this could lead to denial of service conditions where critical commands are indefinitely postponed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-45855. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart