Vulnerability-Lookup

GHSA-CQ4P-Q6C3-FQXH

Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-25 06:30

Details

In the Linux kernel, the following vulnerability has been resolved:

nvme-fc: Do not cancel requests in io target before it is initialized

A new nvme-fc controller in CONNECTING state sees admin request timeout schedules ctrl->ioerr_work to abort inflight requests. This ends up calling __nvme_fc_abort_outstanding_ios() which aborts requests in both admin and io tagsets. In case fc_ctrl->tag_set was not initialized we see the warning below. This is because ctrl.queue_count is initialized early in nvme_fc_alloc_ctrl().

nvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe lpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6). you didn't initialize this object before use? turning off the locking correctness validator. Workqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc] Call Trace: dump_stack_lvl+0x57/0x80 register_lock_class+0x567/0x580 __lock_acquire+0x330/0xb90 lock_acquire.part.0+0xad/0x210 blk_mq_tagset_busy_iter+0xf9/0xc00 __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc] nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc] process_one_work+0x82c/0x1450 worker_thread+0x5ee/0xfd0 kthread+0x3a0/0x750 ret_from_fork+0x439/0x670 ret_from_fork_asm+0x1a/0x30

Update the check in __nvme_fc_abort_outstanding_ios() confirm that io tagset was created before iterating over busy requests. Also make sure to cancel ctrl->ioerr_work before removing io tagset.

Severity

8.8 (High)


                  
                    CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-97409"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-24T17:17:18Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: Do not cancel requests in io target before it is initialized\n\nA new nvme-fc controller in CONNECTING state sees admin request timeout\nschedules ctrl-\u003eioerr_work to abort inflight requests. This ends up\ncalling __nvme_fc_abort_outstanding_ios() which aborts requests in both\nadmin and io tagsets. In case fc_ctrl-\u003etag_set was not initialized we\nsee the warning below. This is because ctrl.queue_count is initialized\nearly in nvme_fc_alloc_ctrl().\n\nnvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss\nINFO: trying to register non-static key.\nThe code is fine but needs lockdep annotation, or maybe\nlpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6).\nyou didn\u0027t initialize this object before use?\nturning off the locking correctness validator.\nWorkqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc]\nCall Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x57/0x80\n register_lock_class+0x567/0x580\n __lock_acquire+0x330/0xb90\n lock_acquire.part.0+0xad/0x210\n blk_mq_tagset_busy_iter+0xf9/0xc00\n __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc]\n nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc]\n process_one_work+0x82c/0x1450\n worker_thread+0x5ee/0xfd0\n kthread+0x3a0/0x750\n ret_from_fork+0x439/0x670\n ret_from_fork_asm+0x1a/0x30\n \u003c/TASK\u003e\n\nUpdate the check in __nvme_fc_abort_outstanding_ios() confirm that io\ntagset was created before iterating over busy requests. Also make sure\nto cancel ctrl-\u003eioerr_work before removing io tagset.",
  "id": "GHSA-cq4p-q6c3-fqxh",
  "modified": "2026-09-25T06:30:31Z",
  "published": "2026-09-24T18:31:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97409"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/da930308b4bc24c335574e85ca84ff70a988cf05"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dd39064d2948b14dbe4f364fe4b3c9cfc632cc21"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ee38469f88492df99e1d97f03aa40ecfd218934f"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-97409 (GCVE-0-2026-97409)

Vulnerability from cvelistv5 – Published: 2026-09-24 16:03 – Updated: 2026-09-25 12:43

Title

nvme-fc: Do not cancel requests in io target before it is initialized

Summary

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: Do not cancel requests in io target before it is initialized A new nvme-fc controller in CONNECTING state sees admin request timeout schedules ctrl->ioerr_work to abort inflight requests. This ends up calling __nvme_fc_abort_outstanding_ios() which aborts requests in both admin and io tagsets. In case fc_ctrl->tag_set was not initialized we see the warning below. This is because ctrl.queue_count is initialized early in nvme_fc_alloc_ctrl(). nvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe lpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6). you didn't initialize this object before use? turning off the locking correctness validator. Workqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc] Call Trace: <TASK> dump_stack_lvl+0x57/0x80 register_lock_class+0x567/0x580 __lock_acquire+0x330/0xb90 lock_acquire.part.0+0xad/0x210 blk_mq_tagset_busy_iter+0xf9/0xc00 __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc] nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc] process_one_work+0x82c/0x1450 worker_thread+0x5ee/0xfd0 kthread+0x3a0/0x750 ret_from_fork+0x439/0x670 ret_from_fork_asm+0x1a/0x30 </TASK> Update the check in __nvme_fc_abort_outstanding_ios() confirm that io tagset was created before iterating over busy requests. Also make sure to cancel ctrl->ioerr_work before removing io tagset.

Severity

8.8 (High)


                        
                          CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux mitre root

References

3 references

URL	Tags
https://git.kernel.org/stable/c/da930308b4bc24c33…
https://git.kernel.org/stable/c/dd39064d2948b14db…
https://git.kernel.org/stable/c/ee38469f88492df99…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 52793d62a696e9188092eb0817fb1219ee5729ff , < da930308b4bc24c335574e85ca84ff70a988cf05 (git) Affected: 52793d62a696e9188092eb0817fb1219ee5729ff , < dd39064d2948b14dbe4f364fe4b3c9cfc632cc21 (git) Affected: 52793d62a696e9188092eb0817fb1219ee5729ff , < ee38469f88492df99e1d97f03aa40ecfd218934f (git)
Linux	Linux	Affected: 5.10 Unaffected: 0 , < 5.10 (semver) Unaffected: 6.12.111 , ≤ 6.12.* (semver) Unaffected: 6.18.53 , ≤ 6.18.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/fc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "da930308b4bc24c335574e85ca84ff70a988cf05",
              "status": "affected",
              "version": "52793d62a696e9188092eb0817fb1219ee5729ff",
              "versionType": "git"
            },
            {
              "lessThan": "dd39064d2948b14dbe4f364fe4b3c9cfc632cc21",
              "status": "affected",
              "version": "52793d62a696e9188092eb0817fb1219ee5729ff",
              "versionType": "git"
            },
            {
              "lessThan": "ee38469f88492df99e1d97f03aa40ecfd218934f",
              "status": "affected",
              "version": "52793d62a696e9188092eb0817fb1219ee5729ff",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/fc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.10"
            },
            {
              "lessThan": "5.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.111",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.53",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.111",
                  "versionStartIncluding": "5.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.53",
                  "versionStartIncluding": "5.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "5.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: Do not cancel requests in io target before it is initialized\n\nA new nvme-fc controller in CONNECTING state sees admin request timeout\nschedules ctrl-\u003eioerr_work to abort inflight requests. This ends up\ncalling __nvme_fc_abort_outstanding_ios() which aborts requests in both\nadmin and io tagsets. In case fc_ctrl-\u003etag_set was not initialized we\nsee the warning below. This is because ctrl.queue_count is initialized\nearly in nvme_fc_alloc_ctrl().\n\nnvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss\nINFO: trying to register non-static key.\nThe code is fine but needs lockdep annotation, or maybe\nlpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6).\nyou didn\u0027t initialize this object before use?\nturning off the locking correctness validator.\nWorkqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc]\nCall Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x57/0x80\n register_lock_class+0x567/0x580\n __lock_acquire+0x330/0xb90\n lock_acquire.part.0+0xad/0x210\n blk_mq_tagset_busy_iter+0xf9/0xc00\n __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc]\n nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc]\n process_one_work+0x82c/0x1450\n worker_thread+0x5ee/0xfd0\n kthread+0x3a0/0x750\n ret_from_fork+0x439/0x670\n ret_from_fork_asm+0x1a/0x30\n \u003c/TASK\u003e\n\nUpdate the check in __nvme_fc_abort_outstanding_ios() confirm that io\ntagset was created before iterating over busy requests. Also make sure\nto cancel ctrl-\u003eioerr_work before removing io tagset."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:A - A rogue NVMe-FC target stalls or errors the admin-queue FCP from nvmf_connect_admin_queue() in nvme_fc_create_association(); nvme_fc_fcpio_done() queues ctrl-\u003eioerr_work, and nvme_fc_ctrl_ioerr_work() -\u003e nvme_fc_error_recovery() (CONNECTING) reaches the patched __nvme_fc_abort_outstanding_ios(). FC/FCoE is a non-routable SAN fabric, so Adjacent.\nAC:L - nvme_fc_alloc_ctrl() sets queue_count \u003e 1 before nvme_alloc_io_tag_set(), so CONNECTING has a zeroed embedded tag_set. The attacker creates that window by not completing the admin Connect FCP until nvme_fc_timeout()/nvme_fc_fcpio_done() runs; __nvme_fc_abort_outstanding_ios() then deterministically calls blk_mq_tagset_busy_iter(\u0026ctrl-\u003etag_set).\nPR:N - The attacker is an unauthenticated NVMe-FC N_Port; the host transport does not authenticate the remote port (fabric zoning only). nvmf-autoconnect writes /dev/nvme-fabrics as root after FC_EVENT=nvmediscovery, so the fabric peer needs no host account or capability.\nUI:N - nvme_fc_register_remoteport() calls nvme_fc_signal_discovery_scan(), which emits KOBJ_CHANGE with FC_EVENT=nvmediscovery; nvmf-autoconnect and nvmefc-boot-connections then write /dev/nvme-fabrics with no interactive administrator. The admin-FCP stall is the attacker\u0027s own action.\nS:U - srcu_read_lock() on the uninitialized tags_srcu and the tag_set teardown UAF corrupt host kernel per-CPU data and blk-mq tag memory in the same kernel; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - blk_mq_tagset_busy_iter() takes srcu_read_lock(\u0026ctrl-\u003etag_set.tags_srcu) on a kzalloc-zeroed tag_set, so __srcu_read_lock() this_cpu_inc()s a NULL srcu_ctrp. After nvme_alloc_io_tag_set(), nvme_fc_create_io_queues()\u0027s error path also calls nvme_remove_io_tag_set() while nvme_reset_wq still iterates the live tag_set \u2014 a heap UAF.\nI:H - The NULL-srcu this_cpu_inc corrupts per-CPU words at offset 0 (x86 current_task is PER_CPU_CACHE_HOT). Concurrent blk_mq_free_tag_set() versus blk_mq_tagset_busy_iter() is a UAF of tag_set-\u003etags and the SRCU sda; slab reuse of those objects yields a write/control-flow primitive.\nA:H - The report is lockdep in blk_mq_tagset_busy_iter() from __nvme_fc_abort_outstanding_ios() on the zeroed tag_set. Without lockdep, this_cpu_inc of a NULL per-CPU pointer and the nvme_remove_io_tag_set() UAF oops or panic the host and take down the NVMe-FC storage path."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-25T12:43:43.689Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/da930308b4bc24c335574e85ca84ff70a988cf05"
        },
        {
          "url": "https://git.kernel.org/stable/c/dd39064d2948b14dbe4f364fe4b3c9cfc632cc21"
        },
        {
          "url": "https://git.kernel.org/stable/c/ee38469f88492df99e1d97f03aa40ecfd218934f"
        }
      ],
      "title": "nvme-fc: Do not cancel requests in io target before it is initialized",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-97409",
    "datePublished": "2026-09-24T16:03:16.195Z",
    "dateReserved": "2026-09-24T14:53:16.867Z",
    "dateUpdated": "2026-09-25T12:43:43.689Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-CQ4P-Q6C3-FQXH

CVE-2026-97409 (GCVE-0-2026-97409)

Tags

Sightings

Nomenclature

Related by attack behaviour