Answer in brief
CVE-2025-23147 records a Medium severity (CVSS 5.5) vulnerability in i3c: Add NULL pointer check in i3c_master_queue_ibi(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <1b54faa5f47fa7c642179744aeff03f0810dc62e || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <09359e7c8751961937cb5fc50220969b0a4e1058 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <3ba402610843d7d15c7f3966a461deeeaff7fba4 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47f || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <6871a676aa534e8f218279672e0445c725f81026 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <e6bba328578feb58c614c11868c259b40484c5fa || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <fe4a4fc179b7898055555a11685915473588392e || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <ff9d61db59bb27d16d3f872bff2620d50856b80c || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <bd496a44f041da9ef3afe14d1d6193d460424e91 | 1b54faa5f47fa7c642179744aeff03f0810dc62e, 09359e7c8751961937cb5fc50220969b0a4e1058, 3ba402610843d7d15c7f3966a461deeeaff7fba4, d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47f, 6871a676aa534e8f218279672e0445c725f81026, e6bba328578feb58c614c11868c259b40484c5fa, fe4a4fc179b7898055555a11685915473588392e, ff9d61db59bb27d16d3f872bff2620d50856b80c, bd496a44f041da9ef3afe14d1d6193d460424e91 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
May 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.