CVE-2026-72409
net: mvneta: re-enable percpu interrupt on resume
Reported by linux · Published August 15, 2026
In the Linux kernel, the following vulnerability has been resolved: net: mvneta: re-enable percpu interrupt on resume On Marvell MPIC platforms (Armada 370/XP/38x), mvneta uses a percpu IRQ disable/enable scheme for NAPI: the ISR (mvneta_percpu_isr) calls disable_percpu_irq() to mask the MPIC per-CPU interrupt and schedules NAPI poll, which calls enable_percpu_irq() on completion to unmask. If suspend occurs while NAPI poll is pending (between disable_percpu_irq in the ISR and enable_percpu_irq in poll completion), the interrupt is never re-enabled: 1. mvneta_percpu_isr: disable_percpu_irq() + napi_schedule() => MPIC masked, percpu_enabled cpumask bit cleared 2. NAPI poll does not complete before suspend proceeds (on PREEMPT_RT this is highly likely since softirqs run in ksoftirqd which gets frozen; on non-RT it can happen when softirq processing is deferred to ksoftirqd) 3. mvneta_stop_dev => napi_disable(): cancels the pending poll without executing the completion path 4. suspend_device_irqs => IRQCHIP_MASK_ON_SUSPEND: masks MPIC (already masked, but records IRQS_SUSPENDED) 5. Resume: mpic_resume checks irq_percpu_is_enabled() => false (bit was cleared in step 1) => skips unmask 6. mvneta_start_dev only restores device-level INTR_NEW_MASK, does not touch the MPIC per-CPU mask Result: MPIC per-CPU interrupt stays masked permanently. The NIC generates interrupts (INTR_NEW_CAUSE != 0) but the CPU never receives them, causing complete loss of network connectivity. Fix by calling on_each_cpu(mvneta_percpu_enable) in the resume path to unconditionally unmask the MPIC per-CPU interrupt regardless of pre-suspend state.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | fd398d6480987e4c84fff0aaab6b9d6642a93343, bf88cd3b649bc3e638f1e8a77649581852747a68, be626ac1faadd49c2cead9f9cd06ba8752d81563, b84dd48f9da1eb132bdc06a944423cd5a1641ef1, 8c7a489aa71d2693752b2e794a68bf672d16c829, 82c13027ed283b856017adee970dbfdffce5c6b8, 5bdb33ff6e58bdc43632e98b30723eb65352d671, 1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 12bb03b436dad56692e9a103ed26156156bef5d2, 12bb03b436dad56692e9a103ed26156156bef5d2, 12bb03b436dad56692e9a103ed26156156bef5d2 |
| Linux | Linux | 4.4, 0, 5.10.261 |
| Linux | Linux | 7.2, 0, 5.10.261 |
| linux | linux_kernel | 4.4, 4.4, 4.4 |
Timeline
- Aug 15, 2026 Coalition ESS Score
- Aug 15, 2026 CVE Published
- Aug 19, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (30 in total, the first dated here)
- Oct 16, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-72409
vulnetix vdb fixes CVE-2026-72409
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72409/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart