xen/events: Return -EEXIST for bound VIRQs (Linux Linux)

CVE-2025-40160
Not available

At a glance

Source
NVD
EPSS
EPSS 0.20 % · percentile 10 ()
State
PUBLISHED
Published
Updated
Assigner
Linux
NVD status
Deferred

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

European references

CERT-FR advisories

Affected products

ProductVersions
Linux · Linuxaffected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 < 7e19b3643855d4b63442bd20e8bb811e1a75998e ; affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 < 612ef6056855c0aacb9b25d1d853c435754483f7 ; affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 < a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa ; affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 < f81db055a793eca9d05f79658ff62adafb41d664 ; affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 < 07ce121d93a5e5fb2440a24da3dbf408fcee978e
Linux · Linuxaffected 3.2 ; unaffected 0 < 3.2 ; unaffected 6.1.191 ≤ 6.1.* ; unaffected 6.6.113 ≤ 6.6.* ; unaffected 6.12.54 ≤ 6.12.* ; unaffected 6.17.4 ≤ 6.17.*

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD