LiveActive security incident?Get immediate response
CVE Record

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

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.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel issue in a staging MOST I2C driver. The driver was broken for years and could crash through a NULL pointer dereference if probed. The upstream resolution was to remove the broken driver. Business impact appears limited unless your kernels include and expose this staging driver.

Executive priority

Handle through normal kernel patch management unless your environment uses custom kernels or staging drivers. Prioritize validation for embedded or automotive-style Linux builds where MOST-related drivers may be intentionally included.

Technical view

The MOST I2C staging driver failed to set the interface device pointer required after commit 723de0f9171e. Registration/probe can dereference NULL. The kernel stable references resolve the issue by removing the broken I2C driver from staging. No CVSS, CWE, or detailed distro impact is provided.

Likely exposure

Likely narrow. Exposure depends on running Linux kernels that include the affected staging MOST I2C driver and a path for it to be probed. The source bundle does not show broad default exposure or affected distributions.

Exploitation context

No active exploitation is stated. The CVE is not listed as KEV in the provided bundle. The described failure is a kernel NULL pointer dereference on probe, but the sources do not provide exploitability details beyond that condition.

Researcher notes

Evidence is limited to the CVE text and kernel stable references. The root cause is a stale staging driver contract after commit 723de0f9171e. The fix is removal, not a behavioral repair. No proof of remote reachability is provided.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check Linux vendor or distribution advisories for packaged kernel status.
  • If updating is delayed, verify the MOST I2C staging driver is not enabled or loaded.
  • Avoid enabling unused staging drivers in production kernels.

Validation and detection

  • Inventory kernel versions and compare against vendor fixed releases.
  • Check kernel configuration and modules for the MOST I2C staging driver.
  • Confirm the relevant stable fix commit is present in your kernel source or package.
  • Review crash logs for NULL pointer dereferences tied to MOST I2C probing.
Prepared
Confidence
medium
Sources
6

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-2025-68755 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
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, 723de0f9171eeb49a3ae98cae82ebbbb992b3a7cunaffected
LinuxLinux5.6, 0, 6.6.120, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

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