CVE-2026-72142 — i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < 38d4947431b2410850409fda016b2ac9f640a4dd≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < e3e8b02d4773cfc5ad561d2e5505efde36c6927a≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < c882e8cc68fb993700dc21fd6e754001e6297934≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < 6d2c973926d0612360693bc559be2ffde836151b≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < 60ed00d46616a9232e42ea7a3e3c0273d7cf7543≥ 8e8782c71595a5ad29e234ce6b3d2fce787fb07a and < cb2fc37857693b55909fb77dc2c87cfbc1cdc476 and 1 moreversion 3.16 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/6d2c973926d0612360693bc559be2ffde836151b
- git.kernel.org/stable/c/c882e8cc68fb993700dc21fd6e754001e6297934
- git.kernel.org/stable/c/016ef0f6ca4bc9bf0330ac41bd2ea349759643e3
- git.kernel.org/stable/c/e3e8b02d4773cfc5ad561d2e5505efde36c6927a
- git.kernel.org/stable/c/38d4947431b2410850409fda016b2ac9f640a4dd
- git.kernel.org/stable/c/0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec
- git.kernel.org/stable/c/60ed00d46616a9232e42ea7a3e3c0273d7cf7543
- git.kernel.org/stable/c/cb2fc37857693b55909fb77dc2c87cfbc1cdc476
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72142 is "i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.