Answer in brief
CVE-2025-40160 records a Unknown severity vulnerability in xen/events: Return -EEXIST for bound VIRQs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=62cc5fc7b2e0218144e162afb8191db9b924b5e6 <7e19b3643855d4b63442bd20e8bb811e1a75998e || >=62cc5fc7b2e0218144e162afb8191db9b924b5e6 <612ef6056855c0aacb9b25d1d853c435754483f7 || >=62cc5fc7b2e0218144e162afb8191db9b924b5e6 <a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa || >=62cc5fc7b2e0218144e162afb8191db9b924b5e6 <f81db055a793eca9d05f79658ff62adafb41d664 || >=62cc5fc7b2e0218144e162afb8191db9b924b5e6 <07ce121d93a5e5fb2440a24da3dbf408fcee978e | 7e19b3643855d4b63442bd20e8bb811e1a75998e, 612ef6056855c0aacb9b25d1d853c435754483f7, a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa, f81db055a793eca9d05f79658ff62adafb41d664, 07ce121d93a5e5fb2440a24da3dbf408fcee978e |
| Linux/Linuxgeneric | 3.2 | Not reported |
Published upstream
Nov 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.