[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050126-CVE-2025-23147-cfd5@gregkh>
Date: Thu, 1 May 2025 14:56:27 +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-23147: i3c: Add NULL pointer check in i3c_master_queue_ibi()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
i3c: Add NULL pointer check in i3c_master_queue_ibi()
The I3C master driver may receive an IBI from a target device that has not
been probed yet. In such cases, the master calls `i3c_master_queue_ibi()`
to queue an IBI work task, leading to "Unable to handle kernel read from
unreadable memory" and resulting in a kernel panic.
Typical IBI handling flow:
1. The I3C master scans target devices and probes their respective drivers.
2. The target device driver calls `i3c_device_request_ibi()` to enable IBI
and assigns `dev->ibi = ibi`.
3. The I3C master receives an IBI from the target device and calls
`i3c_master_queue_ibi()` to queue the target device driver’s IBI
handler task.
However, since target device events are asynchronous to the I3C probe
sequence, step 3 may occur before step 2, causing `dev->ibi` to be `NULL`,
leading to a kernel panic.
Add a NULL pointer check in `i3c_master_queue_ibi()` to prevent accessing
an uninitialized `dev->ibi`, ensuring stability.
The Linux kernel CVE team has assigned CVE-2025-23147 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.1.135 with commit d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47f
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.6.88 with commit 6871a676aa534e8f218279672e0445c725f81026
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.12.24 with commit e6bba328578feb58c614c11868c259b40484c5fa
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.13.12 with commit fe4a4fc179b7898055555a11685915473588392e
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.14.3 with commit ff9d61db59bb27d16d3f872bff2620d50856b80c
Issue introduced in 5.0 with commit 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and fixed in 6.15-rc1 with commit bd496a44f041da9ef3afe14d1d6193d460424e91
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-23147
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/i3c/master.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/d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47f
https://git.kernel.org/stable/c/6871a676aa534e8f218279672e0445c725f81026
https://git.kernel.org/stable/c/e6bba328578feb58c614c11868c259b40484c5fa
https://git.kernel.org/stable/c/fe4a4fc179b7898055555a11685915473588392e
https://git.kernel.org/stable/c/ff9d61db59bb27d16d3f872bff2620d50856b80c
https://git.kernel.org/stable/c/bd496a44f041da9ef3afe14d1d6193d460424e91
Powered by blists - more mailing lists