irqchip/gic-v3-its: Avoid truncating memory addresses
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.249, 5.15.199, 6.1.162, 6.12.68, 6.18.8, 6.6.122
- CVEs
- CVE-2026-23085
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 04:25 UTC · Revision 1
Source evidence
irqchip/gic-v3-its: Avoid truncating memory addresses
core-osv · Original sourcePublished 4 Feb 2026, 16:08 UTC
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.
osv:CVE-2026-23085
Kernel
Fixed versions: 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8
Complete source record
{
"id": "654fc005decdbd40858a0559aeb7cc88566a3ebf1a57571137cdc92816d3db9d",
"url": "https://osv.dev/vulnerability/CVE-2026-23085",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "irqchip/gic-v3-its: Avoid truncating memory addresses",
"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.",
"evidence": "osv:CVE-2026-23085",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.249",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.199",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.162",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.122",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.68",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-23085",
"aliases": [
"CVE-2026-23085"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e"
},
{
"fixed": "e332b3b69e5b3acf07204a4b185071bab15c2b88"
},
{
"fixed": "e2f9c751f73a2d5bb62d94ab030aec118a811f27"
},
{
"fixed": "85215d633983233809f7d4dad163b953331b8238"
},
{
"fixed": "1b323391560354d8c515de8658b057a1daa82adb"
},
{
"fixed": "084ba3b99f2dfd991ce7e84fb17117319ec3cd9f"
},
{
"fixed": "03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98"
},
{
"fixed": "8d76a7d89c12d08382b66e2f21f20d0627d14859"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23085.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.19.0"
},
{
"fixed": "5.10.249"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.199"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.162"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.122"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.68"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23085.json"
}
}
],
"modified": "2026-10-28T02:30:49.641542073Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98",
"https://git.kernel.org/stable/c/084ba3b99f2dfd991ce7e84fb17117319ec3cd9f",
"https://git.kernel.org/stable/c/1b323391560354d8c515de8658b057a1daa82adb",
"https://git.kernel.org/stable/c/85215d633983233809f7d4dad163b953331b8238",
"https://git.kernel.org/stable/c/8d76a7d89c12d08382b66e2f21f20d0627d14859",
"https://git.kernel.org/stable/c/e2f9c751f73a2d5bb62d94ab030aec118a811f27",
"https://git.kernel.org/stable/c/e332b3b69e5b3acf07204a4b185071bab15c2b88",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23085.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-23085",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23085.json"
}
},
"related_cves": [
{
"value": "CVE-2026-23085",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518117,
"published_at": "2026-02-04T16:08:09.368+00:00"
}