PatchSiren cyber security CVE debrief
CVE-2026-90120 Linux CVE debrief
A vulnerability in the Linux kernel's irqchip/gic-v5 component has been addressed. The issue arises from the improper handling of MADT GICC entries that do not correspond to logical CPUs recognized by the kernel, potentially leading to out-of-bounds memory corruption. This problem is resolved by adding a check for the return value of get_logical_index().
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 8.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux kernel maintainers, Linux distribution maintainers, and users of affected Linux kernel versions should assess exposure and apply patches to prevent potential memory corruption.
Why it matters
CVE-2026-90120 is a Linux kernel vulnerability that requires patching to prevent potential memory corruption. Linux kernel maintainers and users should assess exposure and apply patches.
- Potential memory corruption requires verification and patching to prevent system instability.
- Linux kernel maintainers and users must assess exposure and apply patches.
Technical summary
The Linux kernel's irqchip/gic-v5 component has a vulnerability that can lead to out-of-bounds memory corruption when a MADT GICC entry does not correspond to a logical CPU recognized by the kernel. This is due to the unchecked return value of get_logical_index(). The issue has been resolved by adding a check for this return value. The vulnerability requires patching to prevent potential memory corruption. Linux kernel maintainers and users should assess exposure and apply patches. Affected product deployments should be identified and prioritized for patching.
Defensive priority
Linux kernel maintainers and users should assess exposure and apply patches to prevent potential memory corruption.
Recommended defensive actions
- Review and apply Linux kernel patches to ensure get_logical_index() return values are checked.
- Assess system exposure and prioritize patching for affected Linux kernel versions.
- Monitor system logs for potential memory corruption indicators.
- Perform vulnerability scanning to identify potentially affected systems.
- Implement compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Review relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its CVSS score, and references to the Linux kernel patches. The vulnerability arises from the improper handling of MADT GICC entries that do not correspond to logical CPUs recognized by the kernel, potentially leading to out-of-bounds memory corruption. This issue is resolved by adding a check for the return value of get_logical_index(). Linux kernel maintainers and users should assess exposure and apply patches to prevent potential memory corruption. Evidence is based
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90120 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90120
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90120 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90120
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/328affc639ce9873a7a0a3fd6b8339f19767529b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6caeb878f809bdf0aec2fdd96f3d41ef4b69fc69
416baaa9-dc9f-4396-8d5f-8c081fb06d67
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.