[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021435-CVE-2026-23197-59da@gregkh>
Date: Sat, 14 Feb 2026 17:28:54 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23197: i2c: imx: preserve error state in block data length handler
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-23197 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 5f5c2d4579ca6836f5604cca979debd68ecfe23f and fixed in 6.18.10 with commit 3f9b508b3eecc00a243edf320bd83834d6a9b482
Issue introduced in 6.13 with commit 5f5c2d4579ca6836f5604cca979debd68ecfe23f and fixed in 6.19 with commit b126097b0327437048bd045a0e4d273dea2910dd
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-23197
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/i2c/busses/i2c-imx.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/3f9b508b3eecc00a243edf320bd83834d6a9b482
https://git.kernel.org/stable/c/b126097b0327437048bd045a0e4d273dea2910dd
Powered by blists - more mailing lists