VYPR
Unrated severityNVD Advisory· Published Jan 5, 2026· Updated Apr 15, 2026

CVE-2025-68755

CVE-2025-68755

Description

In the Linux kernel, the following vulnerability has been resolved:

staging: most: remove broken i2c driver

The MOST I2C driver has been completely broken for five years without anyone noticing so remove the driver from staging.

Specifically, commit 723de0f9171e ("staging: most: remove device from interface structure") started requiring drivers to set the interface device pointer before registration, but the I2C driver was never updated which results in a NULL pointer dereference if anyone ever tries to probe it.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

The Linux kernel removes the broken MOST I2C driver from staging after five years of being non-functional due to a missing NULL pointer dereference fix.

Vulnerability

Overview

The Linux kernel's staging tree has removed the MOST I2C driver (a driver for Media Oriented Systems Transport over I2C) after it was found to be completely broken for over five years. The problem originated in commit 723de0f9171e ("staging: most: remove device from interface structure"), which introduced a requirement for all MOST drivers to set the interface device pointer before registration. The I2C driver was never updated to meet this requirement, meaning any attempt to probe the device would result in a NULL pointer dereference [1].

Exploitation and

Impact

Because the driver is already in the staging tree (i.e., not fully integrated into the main kernel), exploitation requires a system where the module is loaded and a matching I2C device is present. Under those conditions, probing the driver causes a kernel crash via a NULL pointer dereference. No privilege escalation or memory corruption beyond the immediate crash is described. The impact is limited to denial of service (system crash) in a very specific hardware configuration, and no active exploitation has been reported.

Mitigation

The fix is to remove the driver entirely—no patches are provided for the broken code, as it was deemed more useful to delete the unmaintained, non-functional driver. The commit removing the driver has been applied to the stable kernel tree [2]. Users are advised to update to a kernel version containing this removal. There is no workaround other than not loading the driver or blacklisting the module.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.