CVE-2026-80951: i3c: master: svc: bound IBI payload to the requested max_payload_len
Noroxi assessment
Priority: Monitor (action score 0/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).
- Fixed version: Linux Linux 35aa6730b8c5626b879a4e893fe664f59bf07d7f, 5697d779577e2786ff3348ae9b77020ac0cf0aab, 7c099b0b292a68d0ef558527945dbfb756fbf893.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 35aa6730b8c5626b879a4e893fe664f59bf07d7f, 5697d779577e2786ff3348ae9b77020ac0cf0aab, 7c099b0b292a68d0ef558527945dbfb756fbf893 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: 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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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.12affected
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before 7c099b0b292a68d0ef558527945dbfb756fbf893affected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before 7cc5ba756bc1cfffab9cb2695742f9f479dc73f7affected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before 35aa6730b8c5626b879a4e893fe664f59bf07d7faffected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before f296a0d5907bf88314dfda67245f7f69d1552470affected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before 5697d779577e2786ff3348ae9b77020ac0cf0aabaffected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before aac3c5aababc7fb69d5bf5b0cc52d308574e3a8caffected · git
- dd3c52846d5954acd43f0e771689302f27dadc28 and later · before e2bda39d7f9f285ec803e200b5c1f17143d0b483affected · git
- before 5.12not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80949Sep 11, 2026 · wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control()0Monitor
- ← EarlierCVE-2026-80950Sep 11, 2026 · i3c: renesas: Check that the transfer is valid before accessing it31Monitor
- Later →CVE-2026-80952Sep 11, 2026 · i3c: master: Fix info leak and UAF in device unregister path31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 35aa6730b8c5626b879a4e893fe664f59bf07d7f | Vendor (CNA) |
| Linux Linux | 5697d779577e2786ff3348ae9b77020ac0cf0aab | Vendor (CNA) |
| Linux Linux | 7c099b0b292a68d0ef558527945dbfb756fbf893 | Vendor (CNA) |
| Linux Linux | 7cc5ba756bc1cfffab9cb2695742f9f479dc73f7 | Vendor (CNA) |
| Linux Linux | aac3c5aababc7fb69d5bf5b0cc52d308574e3a8c | Vendor (CNA) |
| Linux Linux | e2bda39d7f9f285ec803e200b5c1f17143d0b483 | Vendor (CNA) |
| Linux Linux | f296a0d5907bf88314dfda67245f7f69d1552470 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5697d779577e2786ff3348ae9b77020ac0cf0aab
- git.kernel.org/stable/c/7c099b0b292a68d0ef558527945dbfb756fbf893
- git.kernel.org/stable/c/7cc5ba756bc1cfffab9cb2695742f9f479dc73f7
- git.kernel.org/stable/c/aac3c5aababc7fb69d5bf5b0cc52d308574e3a8c
- git.kernel.org/stable/c/e2bda39d7f9f285ec803e200b5c1f17143d0b483
- git.kernel.org/stable/c/f296a0d5907bf88314dfda67245f7f69d1552470
Vendor advisories and official records. Exploit/PoC links are deliberately left out.