LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26717: HID: i2c-hid-of: fix NULL-deref on failed power up

In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid-of: fix NULL-deref on failed power up A while back the I2C HID implementation was split in an ACPI and OF part, but the new OF driver never initialises the client pointer which is dereferenced on power-up failures.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26717 is a Linux kernel bug in the I2C HID Open Firmware driver. If device power-up fails, the driver can dereference an uninitialized client pointer and crash that kernel path. The provided sources do not establish remote exploitability, active abuse, or business impact beyond potential stability risk.

Executive priority

Handle as kernel maintenance with targeted urgency for affected Linux device fleets. The available evidence does not support emergency response, but kernel NULL dereferences can affect reliability and should be remediated through normal patch governance.

Technical view

The OF split of the I2C HID implementation did not initialize the client pointer. On power-up failure handling, that pointer could be dereferenced, causing a NULL pointer dereference. Linux stable references document fixes across maintained kernel lines.

Likely exposure

Exposure is most plausible on Linux systems using the i2c-hid-of driver, commonly associated with device-tree/Open Firmware hardware descriptions. Confirm against actual kernel version, vendor backports, and whether the affected driver is present or loaded.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation. It also does not describe a public exploit, remote attack path, privileges required, or attacker-controlled trigger conditions.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability detail, or environmental prerequisites are provided. Analysis should focus on commit provenance, downstream backports, driver configuration, and whether real hardware can reach the failed power-up path.

Mitigation direction

  • Check vendor kernel advisories for CVE-2024-26717 and applicable backports.
  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Prioritize Linux systems that use I2C HID with Open Firmware/device-tree descriptions.
  • Track distribution-specific package names and fixed release notes before deployment.
  • Reboot systems after kernel updates where required by vendor guidance.

Validation and detection

  • Inventory running kernel versions and compare them with vendor CVE guidance.
  • Confirm whether the i2c-hid-of driver is present, built, or loaded.
  • Verify kernel source or package changelog includes one referenced stable commit.
  • Review crash logs for I2C HID power-up NULL dereference traces.
  • Run existing regression tests for HID input devices after kernel updates.
Prepared
Confidence
medium
Sources
7

Public sources used

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-26717 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb33752c300232d7f95dd9a4353947d0c9e6a0e52, b33752c300232d7f95dd9a4353947d0c9e6a0e52, b33752c300232d7f95dd9a4353947d0c9e6a0e52, b33752c300232d7f95dd9a4353947d0c9e6a0e52, b33752c300232d7f95dd9a4353947d0c9e6a0e52unaffected
LinuxLinux5.12, 0, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.