# CVE-2025-68755: staging: most: remove broken i2c driver

> A NULL pointer dereference in the Linux kernel MOST I2C driver causes a system crash if the driver is probed, requiring local access or specific hardware configuration.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-68755, DEBIAN-CVE-2025-68755, GHSA-7g54-f344-23m9, ROOT-OS-DEBIAN-11-CVE-2025-68755, ROOT-OS-DEBIAN-12-CVE-2025-68755, ROOT-OS-DEBIAN-13-CVE-2025-68755, ROOT-OS-UBUNTU-2204-CVE-2025-68755, ROOT-OS-UBUNTU-2404-CVE-2025-68755, UBUNTU-CVE-2025-68755

## What is CVE-2025-68755?

CVE-2025-68755 is a vulnerability in Linux, published on 5 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-68755?


## How do I fix CVE-2025-68755?

Apply the vendor's patch.

## Is CVE-2025-68755 being exploited?

There is no known exploitation of CVE-2025-68755 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68755 and fix it if it is affected.

What it is: CVE-2025-68755 is a vulnerability in Linux, published on 5 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68755 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68755/ (Markdown: https://insights.sbomify.com/CVE-2025-68755/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68755
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68755
- OSV: https://osv.dev/vulnerability/CVE-2025-68755

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68755/
Summaries are generated and may contain mistakes; the official description above is the record.