{"id":"CVE-2026-89907","published":"2026-09-16T11:16:59.703","lastModified":"2026-09-16T15:18:16.810","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Validate MSI data before routing it to EIOINTC\n\npch_msi_set_irq() passes e->msi.data straight into eiointc_set_irq() as\nthe irq number. The MSI data comes from userspace, that either via a\nKVM_IRQ_ROUTING_MSI entry set with KVM_SET_GSI_ROUTING (used by irqfd\nand KVM_IRQ_LINE) or directly via KVM_SIGNAL_MSI, and is never checked\nagainst EIOINTC_IRQS.\n\neiointc_set_irq() uses the value with __set_bit()/__clear_bit() on the\n256-bit isr bitmap, eiointc_update_irq() then indexes sw_coremap[] and\nthe per-cpu coreisr/sw_coreisr bitmaps with it. Therefore a data value\n>= 256 reads and writes memory past the end of those arrays, i.e. any\nprocess holding a VM fd can corrupt kernel memory beyond the allocation\nof loongarch_eiointc.\n\nReject MSI data that doesn't fit in the EIOINTC irq space. The DMSINTC\npath is unaffected as it decodes the vector from the address and masks\nit.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/501514d6ebd2111c353a1296f25dbe22fbd64657","tags":[]},{"url":"https://git.kernel.org/stable/c/83715a40a2d30d23719e0b25380ba82ff905195b","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}