CVE-2026-80951

i3c: master: svc: bound IBI payload to the requested max_payload_len

N/A
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: bound IBI payload to the requested max_payload_len svc_i3c_master_handle_ibi() reads the IBI payload from the RX FIFO into the IBI slot. The loop is bounded by the hardware FIFO size (SVC_I3C_FIFO_SIZE), not by the slot size. slot->data points into the IBI pool, which i3c_generic_ibi_alloc_pool() sizes at max_payload_len per slot. svc_i3c_master_request_ibi() only rejects a max_payload_len larger than SVC_I3C_FIFO_SIZE, so a driver can request a smaller one. mctp-i3c requests 1. Each readsb() then copies the controller RXCOUNT bytes (up to 31) with no check against the slot size. A device that sends more bytes than the slot holds writes past slot->data, an out-of-bounds write into the IBI pool. Bound the loop by dev->ibi->max_payload_len and clamp each read to the space left in the slot, the same way dw-i3c does. A device can still send more than the requested payload. Flush the leftover bytes from the RX FIFO so they do not leak into the next transfer.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.12dd3c52846d5954acd43f0e771689302f27dadc28
Vendor states this is fixed in 35aa6730b8c5626b879a4e893fe664f59bf07d7f (fixed)
Vendor states this is fixed in 5697d779577e2786ff3348ae9b77020ac0cf0aab (fixed)
Vendor states this is fixed in 7c099b0b292a68d0ef558527945dbfb756fbf893 (fixed)
Vendor states this is fixed in 7cc5ba756bc1cfffab9cb2695742f9f479dc73f7 (fixed)
Vendor states this is fixed in aac3c5aababc7fb69d5bf5b0cc52d308574e3a8c (fixed)
Vendor states this is fixed in e2bda39d7f9f285ec803e200b5c1f17143d0b483 (fixed)
Vendor states this is fixed in f296a0d5907bf88314dfda67245f7f69d1552470 (fixed)
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card