CVE-2026-23085irqchip/gic-v3-its: Avoid truncating memory addresses
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 22 days later
· 22 days later
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < e332b3b69e5b3acf07204a4b185071bab15c2b88
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < e2f9c751f73a2d5bb62d94ab030aec118a811f27
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < 85215d633983233809f7d4dad163b953331b8238
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < 1b323391560354d8c515de8658b057a1daa82adb
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < 084ba3b99f2dfd991ce7e84fb17117319ec3cd9f
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < 03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98
- affected cc2d3216f53c9fff0030eb71cacc4ce5f39d1d7e – < 8d76a7d89c12d08382b66e2f21f20d0627d14859
- affected 3.19
- unaffected < 3.19
- unaffected 5.10.249 – ≤ 5.10.*
- unaffected 5.15.199 – ≤ 5.15.*
- unaffected 6.1.162 – ≤ 6.1.*
- unaffected 6.6.122 – ≤ 6.6.*
- unaffected 6.12.68 – ≤ 6.12.*
- unaffected 6.18.8 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References7
- https://git.kernel.org/stable/c/e332b3b69e5b3acf07204a4b185071bab15c2b88 (opens in a new tab)
- https://git.kernel.org/stable/c/e2f9c751f73a2d5bb62d94ab030aec118a811f27 (opens in a new tab)
- https://git.kernel.org/stable/c/85215d633983233809f7d4dad163b953331b8238 (opens in a new tab)
- https://git.kernel.org/stable/c/1b323391560354d8c515de8658b057a1daa82adb (opens in a new tab)
- https://git.kernel.org/stable/c/084ba3b99f2dfd991ce7e84fb17117319ec3cd9f (opens in a new tab)
- https://git.kernel.org/stable/c/03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98 (opens in a new tab)
- https://git.kernel.org/stable/c/8d76a7d89c12d08382b66e2f21f20d0627d14859 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-5457 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23085)Record last updated .