CVE-2024-26751: ARM: ep93xx: Add terminator to gpiod_lookup_table
In the Linux kernel, the following vulnerability has been resolved:
ARM: ep93xx: Add terminator to gpiod_lookup_table
Without the terminator, if a con_id is passed to gpio_find() that
does not exist in the lookup table the function will not stop looping
correctly, and eventually cause an oops.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26751 is a Linux kernel bug in ARM EP93xx GPIO lookup handling. A missing table terminator can make the kernel continue scanning past valid entries and eventually hit a kernel oops. For most organizations, exposure appears limited to systems using affected Linux kernels with EP93xx platform support.
Executive priority
Handle through normal kernel maintenance unless the organization operates EP93xx-based embedded devices. For those systems, patch promptly because a kernel oops can disrupt service availability.
Technical view
The issue is in the ARM ep93xx gpiod_lookup_table. If gpio_find() receives a con_id absent from the lookup table, the unterminated table prevents correct loop termination, leading to an eventual kernel oops. Upstream stable commits add the missing terminator across supported kernel branches.
Likely exposure
Likely narrow. The source identifies Linux kernel versions and commits, but the vulnerable code path is specific to ARM EP93xx GPIO lookup behavior. Exposure is most relevant to embedded or legacy ARM systems running affected kernel branches.
Exploitation context
The bundle does not show active exploitation, public exploit evidence, KEV listing, CVSS, or a CWE. The described failure mode is a kernel oops when an absent con_id is looked up, suggesting availability impact rather than confirmed privilege escalation.
Researcher notes
Evidence is limited to the CVE description, upstream stable references, and Debian LTS advisory linkage. No CVSS, CWE, exploitability assessment, or attack preconditions are provided. Treat impact and reachability as environment-dependent until validated against kernel configuration and device usage.
Mitigation direction
Update affected Linux kernels to versions containing the upstream stable fixes.
Check distribution advisories, including Debian LTS, for packaged kernel updates.
Prioritize EP93xx-based embedded systems and custom ARM kernel builds.
If patching is delayed, monitor affected systems for kernel oops events.
Avoid assuming non-EP93xx systems are exposed without kernel configuration evidence.
Validation and detection
Inventory Linux kernel versions on ARM and embedded fleets.
Confirm whether EP93xx platform support is built or deployed.
Compare deployed kernels against the listed upstream stable fix commits.
Review distro security advisories for backported fixes.
Check kernel logs for related GPIO lookup oops events.
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-26751 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.