CVE-2026-23085 json
irqchip/gic-v3-its: Avoid truncating memory addresses
published 2026-02-04 9 mo ago modified 2026-10-19 20 d ago also EUVD-2026-5457
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.8-1
debian advisories DEBIAN-CVE-2026-23085
- linux Ubuntu 22.04 LTS 5.15.0-176.186
- linux Ubuntu 24.04 LTS 6.8.0-117.117
- linux-aws Ubuntu 22.04 LTS 5.15.0-1105.112
- linux-aws Ubuntu 24.04 LTS 6.8.0-1055.58
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1105.114
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1058.61
- linux-gke Ubuntu 22.04 LTS 5.15.0-1101.107
- linux-gke Ubuntu 24.04 LTS 6.8.0-1054.60
ubuntu advisories UBUNTU-CVE-2026-23085
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-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.34.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.34.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1.150700.17.23.1
suse advisories SUSE-SU-2026:1081-1SUSE-SU-2026:1078-1SUSE-SU-2026:20873-1SUSE-SU-2026:20838-1SUSE-SU-2026:20931-1SUSE-SU-2026:20845-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.27.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.27.1
opensuse advisories openSUSE-SU-2026:20416-1
- git.kernel.org/stable/c/e332b3b69e5b3acf07204a4b185071bab15c2b88 commit
- git.kernel.org/stable/c/e2f9c751f73a2d5bb62d94ab030aec118a811f27 commit
- git.kernel.org/stable/c/85215d633983233809f7d4dad163b953331b8238 commit
- git.kernel.org/stable/c/1b323391560354d8c515de8658b057a1daa82adb commit
- git.kernel.org/stable/c/084ba3b99f2dfd991ce7e84fb17117319ec3cd9f commit
- git.kernel.org/stable/c/03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98 commit
- git.kernel.org/stable/c/8d76a7d89c12d08382b66e2f21f20d0627d14859 commit
Vendor 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-23085 updated cvss 5.5
kernel: irqchip/gic-v3-its: Avoid truncating memory addresses
-
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 kernelaffected: no fix available
-
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
- Technology feeds
References
-
git.kernel.org
/stable/c/e332b3b69e5b3acf07204a4b185071bab15c2b88
patch
-
git.kernel.org
/stable/c/e2f9c751f73a2d5bb62d94ab030aec118a811f27
patch
-
git.kernel.org
/stable/c/85215d633983233809f7d4dad163b953331b8238
patch
-
git.kernel.org
/stable/c/1b323391560354d8c515de8658b057a1daa82adb
patch
-
git.kernel.org
/stable/c/084ba3b99f2dfd991ce7e84fb17117319ec3cd9f
patch
-
git.kernel.org
/stable/c/03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98
patch
-
git.kernel.org
/stable/c/8d76a7d89c12d08382b66e2f21f20d0627d14859
patch
Sources
- CVE List CVE-2026-23085
- NVD CVE-2026-23085
Fencer Vulns 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.