LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23197: i2c: imx: preserve error state in block data length handler

In the Linux kernel, the following vulnerability has been resolved: i2c: imx: preserve error state in block data length handler When a block read returns an invalid length, zero or >I2C_SMBUS_BLOCK_MAX, the length handler sets the state to IMX_I2C_STATE_FAILED. However, i2c_imx_master_isr() unconditionally overwrites this with IMX_I2C_STATE_READ_CONTINUE, causing an endless read loop that overruns buffers and crashes the system. Guard the state transition to preserve error states set by the length handler.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can turn an invalid I2C/SMBus block-read length into an endless read loop, overrunning buffers and crashing the system. Business impact is mainly reliability and availability on affected Linux systems using the i.MX I2C driver, not confirmed data theft or remote compromise from the supplied sources.

Executive priority

Treat as a targeted availability risk for Linux-powered embedded or hardware-integrated systems. Patch in normal-to-accelerated kernel maintenance windows, faster for critical operational devices where a crash would interrupt service or safety processes.

Technical view

In the i2c-imx driver, the block data length handler marks invalid lengths as failed, but i2c_imx_master_isr() overwrites that state with READ_CONTINUE. The fix preserves the failure state so invalid block lengths stop the transfer instead of continuing into buffer overrun and crash behavior.

Likely exposure

Likely exposed systems are Linux kernels in the affected version set that use the i.MX I2C controller path. The source bundle lists Linux 6.13, 6.18.10, and 6.19-related affected entries, but version-range detail is incomplete. Confirm through distro or kernel vendor advisories.

Exploitation context

The supplied sources do not show active exploitation, and KEV is false. The described trigger is an invalid SMBus block-read length reaching the i2c-imx path, causing denial of service through crash. No public exploit steps are provided in the bundle.

Researcher notes

The record lacks CVSS, CWE, and detailed exploitability constraints. Analysis should stay tied to the stated state-machine bug and crash outcome. Confirm exact version ranges from kernel stable trees or downstream advisories before broad asset scoring.

Mitigation direction

  • Apply a Linux kernel or distro update containing the referenced stable fixes.
  • Prioritize i.MX-based embedded, appliance, and industrial systems using I2C/SMBus devices.
  • Check vendor advisories for exact affected kernel builds and backport status.
  • Use operational monitoring for kernel crashes until patched.
  • Avoid inventing local workarounds unless confirmed by the device or OS vendor.

Validation and detection

  • Inventory Linux kernel versions on i.MX-based systems.
  • Confirm whether the i2c-imx driver is built, loaded, or used.
  • Verify installed kernel source or package includes the referenced stable commits.
  • Review crash logs for I2C or SMBus related kernel faults.
  • Track vendor advisory status for affected products and backports.
Prepared
Confidence
medium
Sources
4

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-2026-23197 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
3Source 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
LinuxLinux5f5c2d4579ca6836f5604cca979debd68ecfe23f, 5f5c2d4579ca6836f5604cca979debd68ecfe23funaffected
LinuxLinux6.13, 0, 6.18.10, 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.