Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-23147: i3c: Add NULL pointer check in i3c_master_queue_ibi()

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 09359e7c8751961937cb5fc50220969b0a4e1058, 1b54faa5f47fa7c642179744aeff03f0810dc62e, 3ba402610843d7d15c7f3966a461deeeaff7fba4; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 09359e7c8751961937cb5fc50220969b0a4e1058, 1b54faa5f47fa7c642179744aeff03f0810dc62e, 3ba402610843d7d15c7f3966a461deeeaff7fba4; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Nov 5, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-23147

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.237
  • linux linux kernel5.11 and later · before 5.15.181
  • linux linux kernel5.16 and later · before 6.1.135
  • linux linux kernel5.0 and later · before 5.4.293
  • linux linux kernel6.7 and later · before 6.12.24
  • linux linux kernel6.13 and later · before 6.13.12
  • linux linux kernel6.14 and later · before 6.14.3
  • linux linux kernel6.2 and later · before 6.6.88

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 1b54faa5f47fa7c642179744aeff03f0810dc62eaffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 09359e7c8751961937cb5fc50220969b0a4e1058affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 3ba402610843d7d15c7f3966a461deeeaff7fba4affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before d83b0c03ef8fbea2f03029a1cc1f5041f0e1d47faffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 6871a676aa534e8f218279672e0445c725f81026affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before e6bba328578feb58c614c11868c259b40484c5faaffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before fe4a4fc179b7898055555a11685915473588392eaffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before ff9d61db59bb27d16d3f872bff2620d50856b80caffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before bd496a44f041da9ef3afe14d1d6193d460424e91affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.12.25-16.12.25-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-23144May 1, 2025 · backlight: led_bl: Hold led_access lock when calling led_sysfs_disable()
    22Monitor
  • ← EarlierCVE-2025-23145May 1, 2025 · mptcp: fix NULL pointer in can_accept_new_subflow
    22Monitor
  • Later →CVE-2025-23149May 1, 2025 · tpm: do not start chip while suspended
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux09359e7c8751961937cb5fc50220969b0a4e1058Vendor (CNA)
Linux Linux1b54faa5f47fa7c642179744aeff03f0810dc62eVendor (CNA)
Linux Linux3ba402610843d7d15c7f3966a461deeeaff7fba4Vendor (CNA)
Linux Linux6871a676aa534e8f218279672e0445c725f81026Vendor (CNA)
Linux Linuxbd496a44f041da9ef3afe14d1d6193d460424e91Vendor (CNA)
Linux Linuxd83b0c03ef8fbea2f03029a1cc1f5041f0e1d47fVendor (CNA)
Linux Linuxe6bba328578feb58c614c11868c259b40484c5faVendor (CNA)
Linux Linuxfe4a4fc179b7898055555a11685915473588392eVendor (CNA)
Linux Linuxff9d61db59bb27d16d3f872bff2620d50856b80cVendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.135-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records