CVE-2026-23085None▾ SunlitIn 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Oct 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
0.1% → 0.1%
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.
Linux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < e332b3b69e5b3acf07204a4b185071bab15c2b88Linux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < e2f9c751f73a2d5bb62d94ab030aec118a811f27Linux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < 85215d633983233809f7d4dad163b953331b8238Linux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < 1b323391560354d8c515de8658b057a1daa82adbLinux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < 084ba3b99f2dfd991ce7e84fb17117319ec3cd9fLinux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < 03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98Linux >= cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e < 8d76a7d89c12d08382b66e2f21f20d0627d14859Linux 3.19Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets