{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72409",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72409"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "net: mvneta: re-enable percpu interrupt on resume",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: mvneta: re-enable percpu interrupt on resume\n\nOn Marvell MPIC platforms (Armada 370/XP/38x), mvneta uses a percpu\nIRQ disable/enable scheme for NAPI: the ISR (mvneta_percpu_isr) calls\ndisable_percpu_irq() to mask the MPIC per-CPU interrupt and schedules\nNAPI poll, which calls enable_percpu_irq() on completion to unmask.\n\nIf suspend occurs while NAPI poll is pending (between\ndisable_percpu_irq in the ISR and enable_percpu_irq in poll\ncompletion), the interrupt is never re-enabled:\n\n  1. mvneta_percpu_isr: disable_percpu_irq() + napi_schedule()\n     => MPIC masked, percpu_enabled cpumask bit cleared\n  2. NAPI poll does not complete before suspend proceeds\n     (on PREEMPT_RT this is highly likely since softirqs run in\n     ksoftirqd which gets frozen; on non-RT it can happen when\n     softirq processing is deferred to ksoftirqd)\n  3. mvneta_stop_dev => napi_disable(): cancels the pending poll\n     without executing the completion path\n  4. suspend_device_irqs => IRQCHIP_MASK_ON_SUSPEND: masks MPIC\n     (already masked, but records IRQS_SUSPENDED)\n  5. Resume: mpic_resume checks irq_percpu_is_enabled() => false\n     (bit was cleared in step 1) => skips unmask\n  6. mvneta_start_dev only restores device-level INTR_NEW_MASK,\n     does not touch the MPIC per-CPU mask\n\nResult: MPIC per-CPU interrupt stays masked permanently. The NIC\ngenerates interrupts (INTR_NEW_CAUSE != 0) but the CPU never\nreceives them, causing complete loss of network connectivity.\n\nFix by calling on_each_cpu(mvneta_percpu_enable) in the resume path\nto unconditionally unmask the MPIC per-CPU interrupt regardless of\npre-suspend state.",
  "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-72409"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bf88cd3b649bc3e638f1e8a77649581852747a68"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8c7a489aa71d2693752b2e794a68bf672d16c829"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/82c13027ed283b856017adee970dbfdffce5c6b8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/be626ac1faadd49c2cead9f9cd06ba8752d81563"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b84dd48f9da1eb132bdc06a944423cd5a1641ef1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5bdb33ff6e58bdc43632e98b30723eb65352d671"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fd398d6480987e4c84fff0aaab6b9d6642a93343"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.5,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - Remote traffic on internet-facing Marvell Armada 370/XP/38x routers, NAS, and gateways drives mvneta_percpu_isr/NAPI (race step 1); the highest-impact scenario pairs sustained RX/TX load with automatic suspend/resume, so the attack is initiated from the network.\nAC:L - On PREEMPT_RT (called highly likely in the fix) or when softirq is deferred to ksoftirqd, an attacker can sustain traffic to keep NAPI pending across suspend; no uncontrollable memory layout or rare one-shot victim state is required beyond routine PM cycles.\nPR:N - Sending packets to the mvneta interface requires no credentials; in the strongest scenario suspend/resume is driven by automatic system power management rather than privileged manual action, so no account or capability on the victim is needed.\nUI:N - No victim user action is required beyond normal operation; remote traffic and automatic suspend/resume (or scheduled PM) suffice without anyone mounting devices or confirming prompts.\nS:U - The bug leaves the MPIC per-CPU IRQ permanently masked on the same host kernel/driver boundary; it does not cross VM, container, or IOMMU security domains.\nC:N - This is a driver/IRQ state-management logic error with no out-of-bounds access, use-after-free, or memory disclosure; interrupts stay masked but no kernel memory is read.\nI:N - No data structures or packets are corrupted; the failure mode is a permanently masked interrupt with no write primitive or control-flow hijack potential.\nA:H - After resume the MPIC per-CPU interrupt remains permanently masked, so the NIC never delivers packets despite hardware activity, causing complete and lasting loss of network connectivity until reboot."
    }
  }
}
