CVE-2026-98877 json
irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed
published 19d ago modified 17d ago also EUVD-2026-108723
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed
When accidentally setting “kvm-arm.vgic_v4_enable=1” on a system that has no MSI controller device tree node and GICv4, it results a panic as “gic_domain” is NULL and the kernel attempts to access it.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000028 Mem abort info: ESR = 0x0000000096000006
CPU: 1 UID: 0 PID: 295 Comm: lkvm-static Not tainted 7.1.0-rc4-ge3f15ad3970e #5 PREEMPT Hardware name: linux,dummy-virt (DT) pstate: 81402005 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) pc : __irq_domain_instantiate+0x1d4/0x578 lr : __irq_domain_instantiate+0x1cc/0x578
Set vLPI support to false at init time if the host has no ITS, so it propagates properly to kvm_vgic_global_state.has_gicv4.
Patch / fix
- Linux Linux 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-98877
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98877
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.159.1-1
azure linux advisories AZL-110605
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/3e4cae9f1472ba3c9fe87edee24074618b51f537 commit
- git.kernel.org/stable/c/a2508b8855acc96abe69be73b41b672f1ef12516 commit
- git.kernel.org/stable/c/e79934064be85fc9a3a6434da857307d8b78e33d commit
- git.kernel.org/stable/c/4761493dd663443f7353c184e6fa16e1cb3ac5a1 commit
- git.kernel.org/stable/c/ab233119a19716b8f33e73ea7e092e0eb353cfbf commit
- git.kernel.org/stable/c/c8a911b3b07baa0aeb3dbc4e16a4670bd21bed40 commit
- git.kernel.org/stable/c/e61654fbc3bc5d07ec9fafe29f33e19b2b5d0fd5 commit
Is CVE-2026-98877 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98877 updated cvss 4.7
kernel: irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/3e4cae9f1472ba3c9fe87edee24074618b51f537
- git.kernel.org /stable/c/a2508b8855acc96abe69be73b41b672f1ef12516
- git.kernel.org /stable/c/e79934064be85fc9a3a6434da857307d8b78e33d
- git.kernel.org /stable/c/4761493dd663443f7353c184e6fa16e1cb3ac5a1
- git.kernel.org /stable/c/ab233119a19716b8f33e73ea7e092e0eb353cfbf
- git.kernel.org /stable/c/c8a911b3b07baa0aeb3dbc4e16a4670bd21bed40
- git.kernel.org /stable/c/e61654fbc3bc5d07ec9fafe29f33e19b2b5d0fd5
Sources
- CVE List CVE-2026-98877
- NVD CVE-2026-98877
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.