VulnerabilityPublished 12 Nov 2025Updated 30 Oct 2026

CVE-2025-40160: Linux kernel · xen/events: Return -EEXIST for bound VIRQs

Source GCVE Database

Compare

Authoritative record:CVE-2025-40160

Not known to be exploited · fixed in f81db055a793eca9d05f79658ff62adafb41d664 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Patch: Available – fixed in f81db055a793eca9d05f79658ff62adafb41d664, a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa, 612ef6056855c0aacb9b25d1d853c435754483f7 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-86vm-hhg5-pm6h

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 62cc5fc7b2e0218144e162afb8191db9b924b5e6, < f81db055a793eca9d05f79658ff62adafb41d664	Fixed in f81db055a793eca9d05f79658ff62adafb41d664
LinuxLinux	Affected ≥ 62cc5fc7b2e0218144e162afb8191db9b924b5e6, < a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa	Fixed in a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa
LinuxLinux	Affected ≥ 62cc5fc7b2e0218144e162afb8191db9b924b5e6, < 612ef6056855c0aacb9b25d1d853c435754483f7	Fixed in 612ef6056855c0aacb9b25d1d853c435754483f7
LinuxLinux	Affected ≥ 62cc5fc7b2e0218144e162afb8191db9b924b5e6, < 7e19b3643855d4b63442bd20e8bb811e1a75998e	Fixed in 7e19b3643855d4b63442bd20e8bb811e1a75998e
LinuxLinux	Affected ≥ 62cc5fc7b2e0218144e162afb8191db9b924b5e6, < 07ce121d93a5e5fb2440a24da3dbf408fcee978e	Fixed in 07ce121d93a5e5fb2440a24da3dbf408fcee978e
LinuxLinux	Affected =3.2	Fixed in–

Description

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.

References

Community reviews

Loading reviews…