What’s Vulnerable › Vulnerabilities
CVE-2025-23147: i3c: Add NULL pointer check in i3c_master_queue_ibi()
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2025-05-01 · updated 2026-06-17
- Weakness: CWE-476
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.
Affected products
- Debian Linux: 11.0
- Linux kernel: from 5.0 before 5.4.293; from 5.5 before 5.10.237; from 5.11 before 5.15.181; from 5.16 before 6.1.135; from 6.2 before 6.6.88; from 6.7 before 6.12.24 — fixed in 5.10.237, 5.15.181, 5.4.293, 6.1.135, 6.12.24, 6.13.12
How to fix
Upgrade to a fixed version: Linux kernel 5.10.237, 5.15.181, 5.4.293, 6.1.135. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/09359e7c8751961937cb5fc50220969b0a4e1058
- https://git.kernel.org/stable/c/1b54faa5f47fa7c642179744aeff03f0810dc62e
- https://git.kernel.org/stable/c/3ba402610843d7d15c7f3966a461deeeaff7fba4
- https://git.kernel.org/stable/c/6871a676aa534e8f218279672e0445c725f81026
- https://git.kernel.org/stable/c/bd496a44f041da9ef3afe14d1d6193d460424e91
- https://git.kernel.org/stable/c/d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47f
- https://git.kernel.org/stable/c/e6bba328578feb58c614c11868c259b40484c5fa
- https://git.kernel.org/stable/c/fe4a4fc179b7898055555a11685915473588392e
- https://git.kernel.org/stable/c/ff9d61db59bb27d16d3f872bff2620d50856b80c
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Get alerted when CVE-2025-23147 or the next vulnerability affects your stack