CVE-2025-40160: xen/events: Return -EEXIST for bound VIRQs
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 07ce121d93a5e5fb2440a24da3dbf408fcee978e, 612ef6056855c0aacb9b25d1d853c435754483f7, 7e19b3643855d4b63442bd20e8bb811e1a75998e.
Low priority for now. Upgrade to Linux Linux 07ce121d93a5e5fb2440a24da3dbf408fcee978e, 612ef6056855c0aacb9b25d1d853c435754483f7, 7e19b3643855d4b63442bd20e8bb811e1a75998e 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: xen/events: Return -EEXIST for bound VIRQs Change find_virq() to return -EEXIST when a VIRQ is bound to a different CPU than the one passed in. With that, remove the BUG_ON() from bind_virq_to_irq() to propogate the error upwards. Some VIRQs are per-cpu, but others are per-domain or global. Those must be bound to CPU0 and can then migrate elsewhere. The lookup for per-domain and global will probably fail when migrated off CPU 0, especially when the current CPU is tracked. This now returns -EEXIST instead of BUG_ON(). A second call to bind a per-domain or global VIRQ is not expected, but make it non-fatal to avoid trying to look up the irq, since we don't know which per_cpu(virq_to_irq) it will be in.
- Published
- Nov 12, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
- 3.2affected
- 62cc5fc7b2e0218144e162afb8191db9b924b5e6 and later · before 7e19b3643855d4b63442bd20e8bb811e1a75998eaffected · git
- 62cc5fc7b2e0218144e162afb8191db9b924b5e6 and later · before 612ef6056855c0aacb9b25d1d853c435754483f7affected · git
- 62cc5fc7b2e0218144e162afb8191db9b924b5e6 and later · before a1e7f07ae6b594f1ba5be46c6125b43bc505c5aaaffected · git
- 62cc5fc7b2e0218144e162afb8191db9b924b5e6 and later · before f81db055a793eca9d05f79658ff62adafb41d664affected · git
- 62cc5fc7b2e0218144e162afb8191db9b924b5e6 and later · before 07ce121d93a5e5fb2440a24da3dbf408fcee978eaffected · git
- before 3.2not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.113 and later · up to and including 6.6.*not affected · semver
- 6.12.54 and later · up to and including 6.12.*not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.9.1.160000.2.6 | 6.12.0-160000.9.1.160000.2.6 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
+4
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-2025-40158Nov 12, 2025 · ipv6: use RCU in ip6_output()32Monitor
- ← EarlierCVE-2025-40159Nov 12, 2025 · xsk: Harden userspace-supplied xdp_desc validation31Monitor
- Later →CVE-2025-40161Nov 12, 2025 · mailbox: zynqmp-ipi: Fix SGI cleanup on unbind0Monitor
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 | 07ce121d93a5e5fb2440a24da3dbf408fcee978e | Vendor (CNA) |
| Linux Linux | 612ef6056855c0aacb9b25d1d853c435754483f7 | Vendor (CNA) |
| Linux Linux | 7e19b3643855d4b63442bd20e8bb811e1a75998e | Vendor (CNA) |
| Linux Linux | a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa | Vendor (CNA) |
| Linux Linux | f81db055a793eca9d05f79658ff62adafb41d664 | Vendor (CNA) |
| debian:linux | 6.12.57-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | 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.
No history yet (it accumulates with the daily EPSS job).
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.