CVE-2024-26978: serial: max310x: fix NULL pointer dereference in I2C instantiation
In the Linux kernel, the following vulnerability has been resolved:
serial: max310x: fix NULL pointer dereference in I2C instantiation
When trying to instantiate a max14830 device from userspace:
echo max14830 0x60 > /sys/bus/i2c/devices/i2c-2/new_device
we get the following error:
Unable to handle kernel NULL pointer dereference at virtual address...
...
Call trace:
max310x_i2c_probe+0x48/0x170 [max310x]
i2c_device_probe+0x150/0x2a0
...
Add check for validity of devtype to prevent the error, and abort probe
with a meaningful error message.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26978 is a Linux kernel bug in the max310x serial driver. A bad userspace-triggered I2C device instantiation path can cause a NULL pointer dereference during probing. The main business risk is local denial of service on systems exposing this driver path, not confirmed remote compromise.
Executive priority
Treat this as a targeted kernel stability issue. Patch through normal kernel maintenance, faster for embedded, appliance, or hardware-control systems using I2C serial devices. There is no source-backed evidence of active exploitation in the supplied bundle.
Technical view
The issue is CWE-476 in the Linux kernel max310x I2C probe path. The fix adds validation for the device type before probe continues, avoiding a kernel NULL pointer dereference and returning a meaningful error. The provided sources do not include CVSS scoring or evidence of exploitation.
Likely exposure
Exposure is most likely on Linux systems using or loading the max310x serial driver and allowing userspace I2C device instantiation. General-purpose servers may be unaffected if this hardware driver and I2C path are not present or accessible.
Exploitation context
The CVE source describes a crash triggered through userspace I2C device instantiation. CISA KEV status is false in the bundle, and no cited source reports active exploitation. Evidence supports denial-of-service risk, not privilege escalation or remote exploitation.
Researcher notes
The source bundle is incomplete on scoring and exact distro impact. The strongest facts are the kernel NULL dereference, userspace-triggered I2C instantiation context, and stable commits adding devtype validation. Avoid assuming broader exploitability without local driver, permission, and hardware-path analysis.
Mitigation direction
Update to a vendor kernel containing the referenced stable fix commits.
Check Linux distribution advisories for the exact fixed package for your release.
Restrict unnecessary access to I2C device instantiation interfaces.
Disable or avoid loading the max310x driver where not required.
Prioritize embedded or hardware-facing Linux systems using MAX310x-compatible serial devices.
Validation and detection
Inventory running kernels and compare against vendor fixed versions.
Check whether the max310x driver is built, loaded, or required.
Review whether users can access I2C new-device instantiation paths.
Confirm patched kernels include devtype validation in the max310x I2C probe path.
Monitor kernel logs for max310x probe failures or NULL dereference crashes.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.