Manjunatha Venkatesh bd496a44f0 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. Fixes: 3a379bbcea ("i3c: Add core I3C infrastructure") Cc: stable@vger.kernel.org Link: https://lore.kernel.org/lkml/Z9gjGYudiYyl3bSe@lizhi-Precision-Tower-5810/ Signed-off-by: Manjunatha Venkatesh <manjunatha.venkatesh@nxp.com> Reviewed-by: Frank Li <Frank.Li@nxp.com> Link: https://lore.kernel.org/r/20250326123047.2797946-1-manjunatha.venkatesh@nxp.com Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>		2025-03-31 11:44:00 +02:00
..
master	i3c: master: svc: Fix implicit fallthrough in svc_i3c_master_ibi_work()	2025-03-20 23:02:30 +01:00
device.c	i3c: Add comment for -EAGAIN in i3c_device_do_priv_xfers()	2024-05-23 00:29:19 +02:00
internals.h	i3c: master: Enhance i3c_bus_type visibility for device searching & event monitoring	2024-07-26 14:21:30 +02:00
Kconfig
Makefile
master.c	i3c: Add NULL pointer check in i3c_master_queue_ibi()	2025-03-31 11:44:00 +02:00