{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64430",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64430"
  ],
  "published": "2026-07-25T08:51:45Z",
  "summary": "NTB: epf: Avoid calling pci_irq_vector() from hardirq context",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nNTB: epf: Avoid calling pci_irq_vector() from hardirq context\n\nntb_epf_vec_isr() calls pci_irq_vector() in hardirq context to derive\nthe vector number. pci_irq_vector() calls msi_get_virq() that takes a\nmutex and can therefore trigger \"scheduling while atomic\" splats:\n\n  BUG: scheduling while atomic: kworker/u33:0/55/0x00010001\n  ...\n  Call trace:\n   ...\n   schedule+0x38/0x110\n   schedule_preempt_disabled+0x28/0x50\n   __mutex_lock.constprop.0+0x848/0x908\n   __mutex_lock_slowpath+0x18/0x30\n   mutex_lock+0x4c/0x60\n   msi_domain_get_virq+0xe8/0x138\n   pci_irq_vector+0x2c/0x60\n   ntb_epf_vec_isr+0x28/0x120 [ntb_hw_epf]\n   __handle_irq_event_percpu+0x70/0x3a8\n   handle_irq_event+0x48/0x100\n   handle_edge_irq+0x100/0x1c8\n   ...\n\nCache the Linux IRQ number for vector 0 when vectors are allocated and\nuse it as a base in the ISR. Running the ISR in a threaded IRQ handler\nwould also avoid the problem, but that would be unnecessary here.",
  "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.178",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64430"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/33bba331a4a5fee8b6026fe72eca13cceeec1b7b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/aff271b12a1eb8c8b3da19223ae1a6abe1e8168b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1dba8444ac0100133d72374634f6d7451fff1ccc"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/174a97f21bf9c54fa37ec0f321692e862ea130a3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f71e8d9875069fa73e335f63f02ec6e52e3aaa51"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6350df503897d57c5634f71b0767d48c3b837583"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:24:08Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.5,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - Routed traffic over the standard NTB Netdev interface causes the peer host to ring the victim's PCIe MSI/MSI-X doorbell, so an unauthenticated remote sender can reach the vulnerable interrupt handler.\nAC:L - Every delivered doorbell enters the sleep-capable MSI lookup, and the attacker can repeatedly or concurrently trigger multiple allocated vectors to drive mutex contention.\nPR:N - NTB Netdev traffic and peer doorbells have no victim-side authentication or capability check, so an unauthenticated network sender needs no privileges.\nUI:N - Once the NTB link is deployed, receiving traffic automatically invokes the hardirq handler without victim user action.\nS:U - The resulting failure affects the vulnerable host kernel itself and does not cross a VM, IOMMU, or other security-authority boundary.\nC:N - The bug performs no out-of-bounds access or disclosure and provides no kernel-memory read primitive.\nI:N - The defect is an illegal sleep and mutex wait in hardirq context, with no memory corruption, arbitrary write, or data-modification primitive.\nA:H - Mutex contention in hardirq context can cause scheduling-while-atomic failures, deadlock or hang, and a kernel panic on hardened panic-on-warning systems."
    }
  }
}