CVE-2024-26823: irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems
While refactoring the way the ITSs are probed, the handling of quirks
applicable to ACPI-based platforms was lost. As a result, systems such as
HIP07 lose their GICv4 functionnality, and some other may even fail to
boot, unless they are configured to boot with DT.
Move the enabling of quirks into its_probe_one(), making it common to all
firmware implementations.
Security readout for executives and security teams
Plain-English summary
A Linux kernel regression can disable GICv4 functionality or prevent some ARM systems from booting when they use ACPI firmware. HIP07 is specifically identified. The issue is serious for matching hardware but does not appear broadly applicable to ordinary Linux servers or endpoints.
Executive priority
Treat as high priority for confirmed ACPI-based GICv3 ITS systems because affected machines may lose functionality or fail to boot. Use targeted remediation rather than fleetwide emergency action. Schedule controlled kernel updates with rollback readiness, especially for critical ARM infrastructure.
Technical view
A refactor of GICv3 ITS probing omitted platform-quirk detection for ACPI-based systems. The resolution moves quirk enablement into its_probe_one(), making it common across firmware implementations. The bundle identifies affected Linux 6.6–6.8-era versions, but its version data is ambiguous; confirm exact fixed releases with the kernel or distribution vendor.
Likely exposure
Exposure is concentrated in Linux systems using ARM GICv3 ITS hardware and ACPI-based boot. HIP07 platforms are explicitly affected. Device Tree-booted configurations may avoid the regression. Asset-specific firmware, architecture, kernel, and vendor-backport information is required to determine actual exposure.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Although the supplied CVSS vector describes local, low-complexity, low-privilege impact, the narrative primarily documents lost interrupt-controller functionality and boot failure rather than a demonstrated attack path.
Researcher notes
The source describes a regression restored by three stable commits. Its affected-version array is not sufficiently clear to derive precise ranges safely. The stated confidentiality and integrity impacts are not explained by the narrative, so avoid assuming privilege escalation or data compromise without additional vendor evidence.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix.
Confirm exact fixed versions and backports with the Linux distribution or hardware vendor.
Prioritize systems using ACPI, GICv3 ITS, or HIP07 hardware.
Consider Device Tree boot only when supported and operationally validated.
Test boot and interrupt functionality before broad production rollout.
Validation and detection
Inventory ARM systems, kernel builds, firmware mode, and interrupt-controller hardware.
Determine whether each system boots through ACPI or Device Tree.
Check vendor changelogs for the referenced stable commits or equivalent backports.
Reboot updated representative systems and verify successful startup.
Confirm expected GICv4 and interrupt functionality after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26823 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.