Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 12 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 – < 7e19b3643855d4b63442bd20e8bb811e1a75998e
    • affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 – < 612ef6056855c0aacb9b25d1d853c435754483f7
    • affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 – < a1e7f07ae6b594f1ba5be46c6125b43bc505c5aa
    • affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 – < f81db055a793eca9d05f79658ff62adafb41d664
    • affected 62cc5fc7b2e0218144e162afb8191db9b924b5e6 – < 07ce121d93a5e5fb2440a24da3dbf408fcee978e
  • Linux · Linux

    • affected 3.2
    • unaffected < 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.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40160 badge
[![CVE-2025-40160](https://cveledger.app/badge/CVE-2025-40160.svg)](https://cveledger.app/cve/CVE-2025-40160)

Record last updated .