CVE-2026-23355: Software Security Vulnerability Vulnerability

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8672-3h73-hv9p",
  "modified" : "2026-04-24T21:31:56Z",
  "published" : "2026-03-25T12:30:23Z",
  "aliases" : [ "CVE-2026-23355" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nata: libata: cancel pending work after clearing deferred_qc\n\nSyzbot reported a WARN_ON() in ata_scsi_deferred_qc_work(), caused by\nap->ops->qc_defer() returning non-zero before issuing the deferred qc.\n\nata_scsi_schedule_deferred_qc() is called during each command completion.\nThis function will check if there is a deferred QC, and if\nap->ops->qc_defer() returns zero, meaning that it is possible to queue the\ndeferred qc at this time (without being deferred), then it will queue the\nwork which will issue the deferred qc.\n\nOnce the work get to run, which can potentially be a very long time after\nthe work was scheduled, there is a WARN_ON() if ap->ops->qc_defer() returns\nnon-zero.\n\nWhile we hold the ap->lock both when assigning and clearing deferred_qc,\nand the work itself holds the ap->lock, the code currently does not cancel\nthe work after clearing the deferred qc.\n\nThis means that the following scenario can happen:\n1) One or several NCQ commands are queued.\n2) A non-NCQ command is queued, gets stored in ap->deferred_qc.\n3) Last NCQ command gets completed, work is queued to issue the deferred\n   qc.\n4) Timeout or error happens, ap->deferred_qc is cleared. The queued work is\n   currently NOT canceled.\n5) Port is reset.\n6) One or several NCQ commands are queued.\n7) A non-NCQ command is queued, gets stored in ap->deferred_qc.\n8) Work is finally run. Yet at this time, there is still NCQ commands in\n   flight.\n\nThe work in 8) really belongs to the non-NCQ command in 2), not to the\nnon-NCQ command in 7). The reason why the work is executed when it is not\nsupposed to, is because it was never canceled when ap->deferred_qc was\ncleared in 4). Thus, ensure that we always cancel the work after clearing\nap->deferred_qc.\n\nAnother potential fix would have been to let ata_scsi_deferred_qc_work() do\nnothing if ap->ops->qc_defer() returns non-zero. However, canceling the\nwork when clearing ap->deferred_qc seems slightly more logical, as we hold\nthe ap->lock when clearing ap->deferred_qc, so we know that the work cannot\nbe holding the lock. (The function could be waiting for the lock, but that\nis okay since it will do nothing if ap->deferred_qc is not set.)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23355"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0d12453818c35e1ded84633152c6b05002ae48b9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/58e658763ba2aa9168d8516b98a6314d7461a53e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6c5e8f16b5e8e614e829aaf38619bdd79107bb0a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aac9b27f7c1f2b2cf7f50a9ca633ecbbcaf22af9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-03-25T11:16:34Z"
  }
}