In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: bound IBI payload to the requested max_payload_len… (CVE-2026-80951)
A vulnerability in the Linux kernel's i3c master driver allowed out-of-bounds writes to the IBI pool due to improper bounds checking when reading IBI payloads from the RX FIFO. This could occur if a device sent more bytes than the allocated slot size, potentially leading to memory corruption. The issue has been resolved by bounding the read loop to the requested maximum payload length and flushing leftover bytes to prevent data leakage between transfers.
AI Analysis
Technical Summary
The Linux kernel's i3c master driver function svc_i3c_master_handle_ibi() previously read IBI payload data from the RX FIFO into a slot buffer without properly bounding the read loop by the slot size, instead using the hardware FIFO size. Since the slot size is determined by max_payload_len, which can be smaller than the FIFO size, a device sending more bytes than the slot size could cause out-of-bounds writes into the IBI pool memory. The fix bounds the loop by dev->ibi->max_payload_len and clamps each read to the remaining slot space, also flushing leftover bytes from the RX FIFO to avoid data leakage into subsequent transfers.
Potential Impact
This vulnerability could lead to out-of-bounds memory writes in kernel space, potentially causing memory corruption. While the exact impact is not detailed, such memory corruption could lead to system instability or escalation of privileges if exploited. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly bound the IBI payload reads by the requested max_payload_len and to flush leftover bytes from the RX FIFO. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: bound IBI payload to the requested max_payload_len… (CVE-2026-80951)
Description
A vulnerability in the Linux kernel's i3c master driver allowed out-of-bounds writes to the IBI pool due to improper bounds checking when reading IBI payloads from the RX FIFO. This could occur if a device sent more bytes than the allocated slot size, potentially leading to memory corruption. The issue has been resolved by bounding the read loop to the requested maximum payload length and flushing leftover bytes to prevent data leakage between transfers.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's i3c master driver function svc_i3c_master_handle_ibi() previously read IBI payload data from the RX FIFO into a slot buffer without properly bounding the read loop by the slot size, instead using the hardware FIFO size. Since the slot size is determined by max_payload_len, which can be smaller than the FIFO size, a device sending more bytes than the slot size could cause out-of-bounds writes into the IBI pool memory. The fix bounds the loop by dev->ibi->max_payload_len and clamps each read to the remaining slot space, also flushing leftover bytes from the RX FIFO to avoid data leakage into subsequent transfers.
Potential Impact
This vulnerability could lead to out-of-bounds memory writes in kernel space, potentially causing memory corruption. While the exact impact is not detailed, such memory corruption could lead to system instability or escalation of privileges if exploited. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly bound the IBI payload reads by the requested max_payload_len and to flush leftover bytes from the RX FIFO. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j6x8-pq79-v84j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80951"]
Threat ID: 6aa4a02e55bf5e2cf5a86b6c
Added to database: 09/12/2026, 00:43:26 UTC
Last enriched: 09/12/2026, 01:24:55 UTC
Last updated: 09/12/2026, 02:41:25 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.