Menu

Star on GitHub · 3.2k

CVE-2025-68755

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 s…

Published Jan 5, 2026EPSS 0.19%

Overview

CVE-2025-68755 is a known-severity vulnerability. It was published on January 5, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68755?

CVE-2025-68755 is a known-severity vulnerability. It was published on January 5, 2026.

How severe is CVE-2025-68755?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68755?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68755?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68755 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.