Skip to main content
VulnerabilityPublished Updated

CVE-2026-98877: Linux kernel · irqchip/gic-v4: Don't advertise VLPIs if no ITS is probed

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e79934064be85fc9a3a6434da857307d8b78e33d : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e79934064be85fc9a3a6434da857307d8b78e33d, e61654fbc3bc5d07ec9fafe29f33e19b2b5d0fd5, c8a911b3b07baa0aeb3dbc4e16a4670bd21bed40 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < e79934064be85fc9a3a6434da857307d8b78e33d
Fixed in
  • e79934064be85fc9a3a6434da857307d8b78e33d
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < e61654fbc3bc5d07ec9fafe29f33e19b2b5d0fd5
Fixed in
  • e61654fbc3bc5d07ec9fafe29f33e19b2b5d0fd5
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < c8a911b3b07baa0aeb3dbc4e16a4670bd21bed40
Fixed in
  • c8a911b3b07baa0aeb3dbc4e16a4670bd21bed40
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < ab233119a19716b8f33e73ea7e092e0eb353cfbf
Fixed in
  • ab233119a19716b8f33e73ea7e092e0eb353cfbf
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < a2508b8855acc96abe69be73b41b672f1ef12516
Fixed in
  • a2508b8855acc96abe69be73b41b672f1ef12516
LinuxLinuxAffected
  • ≥ a75460547e13c99762c2f9dbfcdd13ad416f91c5, < 4761493dd663443f7353c184e6fa16e1cb3ac5a1
Fixed in
  • 4761493dd663443f7353c184e6fa16e1cb3ac5a1

AI-suggested

A fix is available and has been applied in the Linux kernel commits identified by the fixedVersions hashes. Users should update their Linux kernel to a version including these commits to resolve the issue. Avoid enabling kvm-arm.vgic_v4_enable=1 on systems without an MSI controller device tree node and GICv4 until patched.

Description

A vulnerability in the Linux kernel's irqchip/gic-v4 subsystem causes a kernel panic when the virtual GICv4 is enabled on a system without an MSI controller device tree node and GICv4 support. This occurs due to a NULL pointer dereference when the kernel attempts to access a non-existent gic_domain. The issue is fixed by disabling vLPI support at initialization if the host has no ITS, preventing the panic.

References

Community reviews

Loading reviews…