data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-89907 in the interactive tracker

CVE-2026-89907

LoongArch: KVM: Validate MSI data before routing it to EIOINTC

8.8 EPSS 0.2% AV:L

Published 2026-09-16 (33 days ago) by the Linux kernel CNA. Subsystem arch/loongarch. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-89907 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.2.6-1Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.6-1Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

pch_msi_set_irq() passes e->msi.data straight into eiointc_set_irq() as the irq number. The MSI data comes from userspace, that either via a KVM_IRQ_ROUTING_MSI entry set with KVM_SET_GSI_ROUTING (used by irqfd and KVM_IRQ_LINE) or directly via KVM_SIGNAL_MSI, and is never checked against EIOINTC_IRQS. eiointc_set_irq() uses the value with __set_bit()/__clear_bit() on the 256-bit isr bitmap, eiointc_update_irq() then indexes sw_coremap[] and the per-cpu coreisr/sw_coreisr bitmaps with it. Therefore a data value >= 256 reads and writes memory past the end of those arrays, i.e. any process holding a VM fd can corrupt kernel memory beyond the allocation of loongarch_eiointc. Reject MSI data that doesn't fit in the EIOINTC irq space. The DMSINTC path is unaffected as it decodes the vector from the address and masks it.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

arch/loongarch/kvm/intc/pch_pic.c

What this is
KERNEL VIRTUAL MACHINE FOR LOONGARCH (KVM/LoongArch)MAINTAINERS section matched on arch/loongarch/kvm/ · kvm@vger.kernel.org · Maintained
Show whether Debian builds this, per release

Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.

  • bookworm, trixie, forky, sid?
?
not established - no Makefile entry for the affected file

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS

Signals

Published
2026-09-16 (33 days ago)source
CVSS
8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it
Attack vector
local (AV:L)source
EPSS
0.17%, higher than 6.3% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
arch/loongarch

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.136.18.57506f03b5f869
6.137.2.583715a40a2d3
6.137.3501514d6ebd2

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:LAttack vector, local
pch_msi_set_irq() is reached only via local KVM VM-fd ioctls on /dev/kvm: KVM_SIGNAL_MSI, or KVM_SET_GSI_ROUTING with a KVM_IRQ_ROUTING_MSI entry then irqfd/KVM_IRQ_LINE. No network, Bluetooth, or physical path supplies the unbounded MSI data.
AC:LAttack complexity, low
A single KVM_SIGNAL_MSI (or irqfd injection after installing a KVM_IRQ_ROUTING_MSI entry) with attacker-chosen msi.data >= 256 deterministically drives __set_bit()/__clear_bit() on isr and indexes sw_coremap[] past EIOINTC_IRQS; the attacker fully controls the irq index with no race or uncontrollable layout.
PR:LPrivileges required, low
Exploitation requires only opening /dev/kvm and holding a VM fd (kvm-group membership on typical LoongArch hosts, or equivalent unprivileged VM access), then creating the in-kernel EIOINTC/PCH-PIC/IPI devices. Init-namespace root is not required.
UI:NUser interaction, none
No victim interaction is required. The attacker creates the in-kernel LoongArch irqchip devices on a VM they control and issues KVM_SIGNAL_MSI or irqfd themselves; no mount, file open, or other user action is needed.
S:CScope, changed
A KVM VM operator corrupts host kernel memory beyond the loongarch_eiointc allocation from the KVM userspace interface, crossing the VM-to-host virtualization boundary rather than confining impact to the attacker's VM security scope.
C:HConfidentiality impact, high
Unbounded msi.data causes out-of-bounds __set_bit()/__clear_bit() on the 256-bit isr bitmap and an out-of-bounds sw_coremap[irq] read past the loongarch_eiointc object. Per kernel guidance such OOB memory corruption is High confidentiality impact.
I:HIntegrity impact, high
The attacker fully controls the bit index via 32-bit MSI data, yielding arbitrary-offset bit set/clear from s->isr and further OOB writes into coreisr/sw_coreisr when a valid vCPU id is observed. That out-of-bounds write is usable for host privilege escalation.
A:HAvailability impact, high
Indexing the EIOINTC bitmaps and sw_coremap[] with irq >= 256 can immediately oops or panic the host kernel, and corrupting adjacent slab objects breaks later irq injection, denying service to the host and co-resident VMs.