PatchSiren cyber security CVE debrief
CVE-2026-23085 Linux CVE debrief
The Linux kernel has a vulnerability in the irqchip/gic-v3-its driver that could cause truncation of memory addresses on 32-bit machines with CONFIG_ARM_LPAE. This issue has been resolved by changing the itt_addr variable to the correct phys_addr_t type. The vulnerability could lead to system crashes or instability if exploited. Defenders should assess exposure and verify the presence of the fix in their Linux kernel versions, especially for systems running on 32-bit architectures with CONFIG_ARM_LPAE enabled.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-02-04
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-02-04
- Advisory updated
- 2026-10-19
Who should care
Defenders responsible for Linux kernel-based systems, especially those running 32-bit architectures with CONFIG_ARM_LPAE enabled, should assess exposure and verify the presence of the fix.
Why it matters
The Linux kernel irqchip/gic-v3-its driver vulnerability could cause truncation of memory addresses on 32-bit machines with CONFIG_ARM_LPAE, potentially leading to system crashes or instability.
- Verify Linux kernel versions for the presence of the fix
- Assess exposure for systems running 32-bit architectures with CONFIG_ARM_LPAE enabled
- Update Linux kernel to a version that includes the fix if necessary
- Monitor for potential issues related to memory address truncation
Technical summary
The irqchip/gic-v3-its driver in the Linux kernel has a vulnerability that could cause truncation of memory addresses on 32-bit machines with CONFIG_ARM_LPAE. The fix changes the itt_addr variable to the correct phys_addr_t type, preventing truncation of memory addresses. This change ensures that the driver can handle memory addresses above the 32-bit address limit, preventing system crashes or instability. Defenders should prioritize verifying the presence of this fix in their Linux kernel versions, especially for systems running on 32-bit architectures with CONFIG_ARM_LPAE enabled.
Defensive priority
Defenders should prioritize verifying the presence of this fix in their Linux kernel versions, especially for systems running on 32-bit architectures with CONFIG_ARM_LPAE enabled.
Recommended defensive actions
- Verify Linux kernel versions and check for the presence of the fix
- Assess exposure for systems running 32-bit architectures with CONFIG_ARM_LPAE enabled
- Update Linux kernel to a version that includes the fix if necessary
- Monitor for potential issues related to memory address truncation
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and source item provide details about the vulnerability and its fix in the Linux kernel. The NVD entry is currently not provided. The vulnerability was introduced in the irqchip/gic-v3-its driver, which is used in the Linux kernel. The fix changes the itt_addr variable to the correct phys_addr_t type, preventing truncation of memory addresses. Defenders should verify the presence of this fix in their Linux kernel versions, especially for systems running on 32-bit architectures with CONFIG_ARM_LPAE enabled.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-23085 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-23085
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-23085 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-23085
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
irqchip/gic-v3-its: Avoid truncating memory addresses
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23085.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e332b3b69e5b3acf07204a4b185071bab15c2b88
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e2f9c751f73a2d5bb62d94ab030aec118a811f27
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/85215d633983233809f7d4dad163b953331b8238
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1b323391560354d8c515de8658b057a1daa82adb
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/084ba3b99f2dfd991ce7e84fb17117319ec3cd9f
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/03faa61eb4b9ca9aa09bd91d4c3773d8e7b1ac98
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/8d76a7d89c12d08382b66e2f21f20d0627d14859
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.