i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)
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 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3, 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec, 38d4947431b2410850409fda016b2ac9f640a4dd.
Low priority for now. Upgrade to Linux Linux 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3, 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec, 38d4947431b2410850409fda016b2ac9f640a4dd 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: i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) SMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the atomic (polling) path rejects it as -EPROTO. Worse, it returns without a NACK+STOP: the next receive cycle has already started, so the target keeps holding SDA and the bus stays stuck until a power cycle for this i2c controller. Reading I2DR to obtain the count likewise arms the next byte on the count > I2C_SMBUS_BLOCK_MAX path, which also returned -EPROTO directly and left the bus held. Handle both: NACK the in-flight dummy byte (TXAK) and extend msgs->len so the existing last-byte handling emits STOP; the dummy byte is discarded. A count of 0 is a valid empty block read; a count above I2C_SMBUS_BLOCK_MAX is still reported as -EPROTO, but only after the bus has been released. The interrupt-driven path has the same flaw from a later commit and is fixed separately, as it carries a different Fixes: tag and stable range.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 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
- 3.16affected
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ecaffected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before 38d4947431b2410850409fda016b2ac9f640a4ddaffected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before e3e8b02d4773cfc5ad561d2e5505efde36c6927aaffected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3affected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before c882e8cc68fb993700dc21fd6e754001e6297934affected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before 6d2c973926d0612360693bc559be2ffde836151baffected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before 60ed00d46616a9232e42ea7a3e3c0273d7cf7543affected · git
- 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and later · before cb2fc37857693b55909fb77dc2c87cfbc1cdc476affected · git
- before 3.16not 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3 | Vendor (CNA) |
| Linux Linux | 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec | Vendor (CNA) |
| Linux Linux | 38d4947431b2410850409fda016b2ac9f640a4dd | Vendor (CNA) |
| Linux Linux | 60ed00d46616a9232e42ea7a3e3c0273d7cf7543 | Vendor (CNA) |
| Linux Linux | 6d2c973926d0612360693bc559be2ffde836151b | Vendor (CNA) |
| Linux Linux | c882e8cc68fb993700dc21fd6e754001e6297934 | Vendor (CNA) |
| Linux Linux | cb2fc37857693b55909fb77dc2c87cfbc1cdc476 | Vendor (CNA) |
| Linux Linux | e3e8b02d4773cfc5ad561d2e5505efde36c6927a | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-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).
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 (7 more)Show less
- git.kernel.org/stable/c/0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec
- git.kernel.org/stable/c/38d4947431b2410850409fda016b2ac9f640a4dd
- git.kernel.org/stable/c/60ed00d46616a9232e42ea7a3e3c0273d7cf7543
- git.kernel.org/stable/c/6d2c973926d0612360693bc559be2ffde836151b
- git.kernel.org/stable/c/c882e8cc68fb993700dc21fd6e754001e6297934
- git.kernel.org/stable/c/cb2fc37857693b55909fb77dc2c87cfbc1cdc476
- git.kernel.org/stable/c/e3e8b02d4773cfc5ad561d2e5505efde36c6927a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.