i3c: Add NULL pointer check in i3c_master_queue_ibi()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 · < e6bba328578feb58c614c11868c259b40484c5fa| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's I3C master driver can dereference a NULL pointer when it receives an in-band interrupt (IBI) from a target device before that device has been probed and its IBI handler initialized. This can cause a kernel panic; the input does not establish whether an attacker can trigger it or specify authentication or user-interaction requirements.
Engineers running Linux kernels with I3C master support should check their versions against the vendor advisory; affected versions are not specified.