https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 07:27:36 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23085 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>irqchip/gic-v3-its: Avoid truncating memory addresses</p> <p>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.</p> <p>This caused the qemu virt model to crash in the GICv3 driver, which allocates the &#39;itt&#39; 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 &#39;unsigned long&#39; variable.</p> <p>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.</p> <p>The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don&#39;t call virt_to_phys or similar interfaces. It&#39;s expected that other device drivers have similar issues, but fixing this one is sufficient for booting a virtio based guest.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>irqchip/gic-v3-its: Avoid truncating memory addresses</p> <p>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.</p> <p>This caused the qemu virt model to crash in the GICv3 driver, which allocates the &#39;itt&#39; 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 &#39;unsigned long&#39; variable.</p> <p>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.</p> <p>The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don&#39;t call virt_to_phys or similar interfaces. It&#39;s expected that other device drivers have similar issues, but fixing this one is sufficient for booting a virtio based guest.</p> https://vulnerability.circl.lu/vuln/cve-2026-23085