CVE-2026-72409: net: mvneta: re-enable percpu interrupt on resume
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6, 5bdb33ff6e58bdc43632e98b30723eb65352d671, 82c13027ed283b856017adee970dbfdffce5c6b8.
Low priority for now. Upgrade to Linux Linux 1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6, 5bdb33ff6e58bdc43632e98b30723eb65352d671, 82c13027ed283b856017adee970dbfdffce5c6b8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.4affected
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before bf88cd3b649bc3e638f1e8a77649581852747a68affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before 8c7a489aa71d2693752b2e794a68bf672d16c829affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before 82c13027ed283b856017adee970dbfdffce5c6b8affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before be626ac1faadd49c2cead9f9cd06ba8752d81563affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before 1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before b84dd48f9da1eb132bdc06a944423cd5a1641ef1affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before 5bdb33ff6e58bdc43632e98b30723eb65352d671affected · git
- 12bb03b436dad56692e9a103ed26156156bef5d2 and later · before fd398d6480987e4c84fff0aaab6b9d6642a93343affected · git
- before 4.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72405Aug 15, 2026 · net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync31Monitor
- ← EarlierCVE-2026-72406Aug 15, 2026 · net: sungem: fix probe error cleanup31Monitor
- Later →CVE-2026-72413Aug 15, 2026 · sctp: fix err_chunk memory leaks in INIT handling0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1cc312dc8bc78fa24c80d5bc193dbf5b57a99cc6 | Vendor (CNA) |
| Linux Linux | 5bdb33ff6e58bdc43632e98b30723eb65352d671 | Vendor (CNA) |
| Linux Linux | 82c13027ed283b856017adee970dbfdffce5c6b8 | Vendor (CNA) |
| Linux Linux | 8c7a489aa71d2693752b2e794a68bf672d16c829 | Vendor (CNA) |
| Linux Linux | b84dd48f9da1eb132bdc06a944423cd5a1641ef1 | Vendor (CNA) |
| Linux Linux | be626ac1faadd49c2cead9f9cd06ba8752d81563 | Vendor (CNA) |
| Linux Linux | bf88cd3b649bc3e638f1e8a77649581852747a68 | Vendor (CNA) |
| Linux Linux | fd398d6480987e4c84fff0aaab6b9d6642a93343 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5bdb33ff6e58bdc43632e98b30723eb65352d671
- git.kernel.org/stable/c/82c13027ed283b856017adee970dbfdffce5c6b8
- git.kernel.org/stable/c/8c7a489aa71d2693752b2e794a68bf672d16c829
- git.kernel.org/stable/c/b84dd48f9da1eb132bdc06a944423cd5a1641ef1
- git.kernel.org/stable/c/be626ac1faadd49c2cead9f9cd06ba8752d81563
- git.kernel.org/stable/c/bf88cd3b649bc3e638f1e8a77649581852747a68
- git.kernel.org/stable/c/fd398d6480987e4c84fff0aaab6b9d6642a93343
Vendor advisories and official records. Exploit/PoC links are deliberately left out.