Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-45855ata: libata-scsi: avoid Non-NCQ command starvation

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 94.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-45855
Debian:13linux6.12.85-1DEBIAN-CVE-2026-45855
Debian:14linux6.18.14-1DEBIAN-CVE-2026-45855
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux6.8.0-136.136UBUNTU-CVE-2026-45855
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-aws6.8.0-1061.64UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1061.64~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gcp6.8.0-1064.72UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1064.72~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gke6.8.0-1059.67UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1046.50UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-ibm6.8.0-1061.62UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1061.62~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-136.136.2UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-136.136.2~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1059.62UBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1059.62~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1059.62.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1030.31UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oracle6.8.0-1058.61UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-raspi6.8.0-1061.65UBUNTU-CVE-2026-45855
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45855
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-136.136~22.04.3UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-45855
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1033.34UBUNTU-CVE-2026-45855
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-45855

Affected products (as reported)

VendorProductVersions
Linux Linux bdb01301f3ea51a59eff252b06643fc1fe843e57 – before c475bfce918dc413c4d59b97710b94b1c955ea5fbdb01301f3ea51a59eff252b06643fc1fe843e57 – before ce22aaed011206fed9cbd8c9c2d44718607f31eebdb01301f3ea51a59eff252b06643fc1fe843e57 – before 888cd7e40adb2ef4af1b4d3b6e2e83ad409ae8c2bdb01301f3ea51a59eff252b06643fc1fe843e57 – before 5d61a38a60e62750526d94663b69b7ac5c7f07a5bdb01301f3ea51a59eff252b06643fc1fe843e57 – before 0ea84089dbf62a92dc7889c79e6b18fc89260808
Linux Linux 5.10

References