Skip to main content
VulnerabilityPublished Updated

CVE-2026-23085: Linux kernel · irqchip/gic-v3-its: Avoid truncating memory addresses

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e332b3b69e5b3acf07204a4b185071bab15c2b88 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in e332b3b69e5b3acf07204a4b185071bab15c2b88, e2f9c751f73a2d5bb62d94ab030aec118a811f27, 85215d633983233809f7d4dad163b953331b8238 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 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
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < e332b3b69e5b3acf07204a4b185071bab15c2b88
Fixed in
  • e332b3b69e5b3acf07204a4b185071bab15c2b88
LinuxLinuxAffected
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < e2f9c751f73a2d5bb62d94ab030aec118a811f27
Fixed in
  • e2f9c751f73a2d5bb62d94ab030aec118a811f27
LinuxLinuxAffected
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < 85215d633983233809f7d4dad163b953331b8238
Fixed in
  • 85215d633983233809f7d4dad163b953331b8238
LinuxLinuxAffected
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < 084ba3b99f2dfd991ce7e84fb17117319ec3cd9f
Fixed in
  • 084ba3b99f2dfd991ce7e84fb17117319ec3cd9f
LinuxLinuxAffected
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < 8d76a7d89c12d08382b66e2f21f20d0627d14859
Fixed in
  • 8d76a7d89c12d08382b66e2f21f20d0627d14859
LinuxLinuxAffected
  • ≥ cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e, < 03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98
Fixed in
  • 03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drivers have similar issues, but fixing this one is sufficient for booting a virtio based guest.

References

Community reviews

Loading reviews…