{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-26769",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-26769"
  ],
  "published": "2024-04-03T17:31:22Z",
  "summary": "nvmet-fc: avoid deadlock on delete association path",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid deadlock on delete association path\n\nWhen deleting an association the shutdown path is deadlocking because we\ntry to flush the nvmet_wq nested. Avoid this by deadlock by deferring\nthe put work into its own work item.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.80",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-26769"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5e0bc09a52b6169ce90f7ac6e195791adb16cec4"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1d86f79287206deec36d63b89c741cf542b6cadd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/710c69dbaccdac312e32931abcb8499c1525d397"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.5,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - nvmet-fc is the in-kernel NVMe-over-Fibre-Channel target; the association-delete path is driven by FC-NVMe Link Service traffic (Create/Disconnect Association) received from a remote initiator via `nvmet_fc_rcv_ls_req()`, and the deadlocking put occurs in the completion of the target-generated Disconnect Association LS. This matches the treatment of other NVMe target transports (nvmet-tcp/nvmet-fc) as network-reachable, and is consistent with CVE-2025-40171 on the same code.\nAC:L - A remote peer controls both sides of the race \u2014 it repeatedly creates associations and issues Disconnect Association LSes (or drops connectivity, triggering `nvmet_fc_invalidate_host()`), driving `del_work` and the LS completion onto `nvmet_wq` at will while the targetport reference count is winding down. No memory grooming or attacker-independent condition is required, and the trigger can be retried indefinitely.\nPR:N - FC-NVMe Link Service handling (`nvmet_fc_handle_ls_rqst()` \u2192 `nvmet_fc_ls_create_association()`/`nvmet_fc_ls_disconnect()`) runs before any NVMe-level authentication \u2014 it is the connect handshake itself, so no credentials or privileges are needed to reach the vulnerable teardown path.\nUI:N - The deadlock is reached purely through LS traffic processed asynchronously on `nvmet_wq` plus normal target-port teardown; no action by a local user or administrator on the victim is required to trigger it.\nS:U - The deadlock is confined to the kernel's NVMe target subsystem and its workqueue; no security boundary (VM, IOMMU, sandbox) is crossed and no other security authority's resources are affected.\nC:N - The bug is a nested workqueue flush that hangs; there is no out-of-bounds read, no use-after-free, and no path by which memory contents are exposed to the attacker.\nI:N - No memory is corrupted and no data is modified \u2014 the fix merely defers an existing `kref_put()` into its own work item, so there is no write primitive or control-flow impact.\nA:H - `fcloop_targetport_delete()` calls `flush_work()` on the work item that is itself executing, deadlocking a `nvmet_wq` kworker permanently; this wedges the shared WQ_MEM_RECLAIM `nvmet_wq` used by all nvmet transports and blocks `nvmet_fc_unregister_targetport()`/`nvmet_fc_exit_module()` in `flush_workqueue()` forever, requiring a reboot."
    }
  }
}