[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072555-CVE-2025-38425-d34f@gregkh>
Date: Fri, 25 Jul 2025 16:16:58 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38425: i2c: tegra: check msg length in SMBUS block read
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
i2c: tegra: check msg length in SMBUS block read
For SMBUS block read, do not continue to read if the message length
passed from the device is '0' or greater than the maximum allowed bytes.
The Linux kernel CVE team has assigned CVE-2025-38425 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.142 with commit c39d1a9ae4ad66afcecab124d7789722bfe909fa
Fixed in 6.6.95 with commit be5f6a65509cd5675362f15eb0440fb28b0f9d64
Fixed in 6.12.35 with commit 75a864f21ceeb8c1e8ce1b7589174fec2c3a039e
Fixed in 6.15.4 with commit 3f03f77ce688d02da284174e1884b6065d6159bd
Fixed in 6.16-rc1 with commit a6e04f05ce0b070ab39d5775580e65c7d943da0b
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-2025-38425
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-tegra.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/c39d1a9ae4ad66afcecab124d7789722bfe909fa
https://git.kernel.org/stable/c/be5f6a65509cd5675362f15eb0440fb28b0f9d64
https://git.kernel.org/stable/c/75a864f21ceeb8c1e8ce1b7589174fec2c3a039e
https://git.kernel.org/stable/c/3f03f77ce688d02da284174e1884b6065d6159bd
https://git.kernel.org/stable/c/a6e04f05ce0b070ab39d5775580e65c7d943da0b
Powered by blists - more mailing lists