CVE-2026-45855

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

ata: libata-scsi: avoid Non-NCQ command starvation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce22aaed011206fed9cbd8c9c2d44718607f31ee
generic

ata: libata-scsi: avoid Non-NCQ command starvation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/888cd7e40adb2ef4af1b4d3b6e2e83ad409ae8c2
generic

ata: libata-scsi: avoid Non-NCQ command starvation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d61a38a60e62750526d94663b69b7ac5c7f07a5
generic

ata: libata-scsi: avoid Non-NCQ command starvation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ea84089dbf62a92dc7889c79e6b18fc89260808

Vendor Advisories for CVE-2026-45855(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)6.18.14-1

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 5× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 05:52 UTCEG score recompute
  11. 2026-08-25 05:52 UTCVendor advisory
  12. 2026-08-25 05:52 UTCGHSA enrichment
  13. 2026-08-23 15:40 UTCEG score recompute
  14. 2026-08-23 15:40 UTCVendor advisory
  15. 2026-08-23 15:39 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 21:02 UTCEG score recompute
  19. 2026-08-21 21:02 UTCVendor advisory
  20. 2026-08-21 21:01 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 17:46 UTCEG score recompute
  23. 2026-08-20 17:46 UTCVendor advisory
  24. 2026-08-20 17:46 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 09:22 UTCEG score recompute
  4. 2026-08-17 09:22 UTCVendor advisory
  5. 2026-08-17 09:22 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:56 UTCEG score recompute
  8. 2026-08-16 02:56 UTCVendor advisory
  9. 2026-08-16 02:56 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 23:32 UTCVendor advisory
  13. 2026-08-14 23:32 UTCGHSA enrichment
  14. 2026-08-14 01:35 UTCEG score recompute
  15. 2026-08-14 01:35 UTCVendor advisory
  16. 2026-08-14 01:35 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 20:13 UTCEG score recompute
  19. 2026-08-12 20:13 UTCVendor advisory
  20. 2026-08-12 20:13 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 22:17 UTCEG score recompute
  23. 2026-08-11 22:17 UTCVendor advisory
  24. 2026-08-11 22:17 UTCGHSA enrichment
  25. 2026-08-11 00:15 UTCEG score recompute
  26. 2026-08-11 00:15 UTCVendor advisory
  27. 2026-08-11 00:15 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-09 20:00 UTCEG score recompute
  30. 2026-08-09 20:00 UTCVendor advisory
  31. 2026-08-09 20:00 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-08 22:04 UTCVendor advisory
  34. 2026-08-08 22:04 UTCGHSA enrichment
  35. 2026-08-07 16:49 UTCEG score recompute
  36. 2026-08-07 16:49 UTCVendor advisory
  37. 2026-08-07 16:49 UTCGHSA enrichment
  38. 2026-08-06 18:53 UTCEG score recompute
  39. 2026-08-06 18:53 UTCVendor advisory
  40. 2026-08-06 18:53 UTCGHSA enrichment
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-05 20:56 UTCEG score recompute
  43. 2026-08-05 20:56 UTCVendor advisory
  44. 2026-08-05 20:56 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-03 16:30 UTCEG score recompute
  49. 2026-08-03 16:30 UTCVendor advisory
  50. 2026-08-03 16:30 UTCGHSA enrichment
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 13:46 UTCEG score recompute
  53. 2026-08-02 13:46 UTCVendor advisory
  54. 2026-08-02 13:46 UTCGHSA enrichment
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 15:49 UTCEG score recompute
  57. 2026-08-01 15:49 UTCVendor advisory
  58. 2026-08-01 15:49 UTCGHSA enrichment
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-31 08:07 UTCEG score recompute
  61. 2026-07-31 08:07 UTCVendor advisory
  62. 2026-07-31 08:07 UTCGHSA enrichment
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-29 15:57 UTCEG score recompute
  66. 2026-07-29 15:57 UTCGHSA enrichment
  67. 2026-07-28 15:36 UTCEPSS rescore
  68. 2026-07-27 14:13 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 06:12 UTCOSV refresh
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 03:16 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45855?
CVE-2026-45855 is a medium vulnerability published on May 27, 2026. 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, atascsiqc_issue() indicates to the SCSI layer that the command issuing should be deferred by returning…
When was CVE-2026-45855 disclosed?
CVE-2026-45855 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45855 actively exploited?
CVE-2026-45855 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.0% of all scored CVEs.
What is the CVSS score of CVE-2026-45855?
CVE-2026-45855 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45855?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45855, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45855

Explore →

Is Your Infrastructure Affected by CVE-2026-45855?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.