CVE-2026-72141
Last modified
CVE-2026-72141 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: i2c: imx: fix locked bus on SMBus block-read of 0 (IRQ) SMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the interrupt-driven block-read state machine 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 of this i2c controller. Accept count=0: NACK the in-flight dummy byte (TXAK) and set msg->len to 2 so i2c_imx_isr_read_continue() emits STOP via its normal last-byte path. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: i2c: imx: fix locked bus on SMBus block-read of 0 (IRQ) SMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the interrupt-driven block-read state machine 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 of this i2c controller. Accept count=0: NACK the in-flight dummy byte (TXAK) and set msg->len to 2 so i2c_imx_isr_read_continue() emits STOP via its normal last-byte path. The dummy byte is discarded; block-read callers only consume buf[0..count-1]. Reading I2DR has likewise already armed the next byte on the count > I2C_SMBUS_BLOCK_MAX error path, so NACK it (TXAK) before aborting with -EPROTO; otherwise the failing transfer's STOP cannot complete and the bus stays held. The atomic path regressed earlier (v3.16) and is fixed separately; this patch covers only the v6.13 state-machine rework.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 5f5c2d4579ca6836f5604cca979debd68ecfe23f, < 5d3240f42a667e29262aff76fdebfcdac4980626; >= 5f5c2d4579ca6836f5604cca979debd68ecfe23f, < 56ddfc18ea8f7d77747658892873eb632b2ed530; >= 5f5c2d4579ca6836f5604cca979debd68ecfe23f, < 07fd9385f0d87dff4b34f355f68adf701080cb24 |
| Linux | Linux | 6.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72141?
How severe is CVE-2026-72141?
How do I fix CVE-2026-72141?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72136In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-72137In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72138In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72139In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-7214A vulnerability was identified in eghuzefa engineer-your-dat…7.3
- CVE-2026-72140In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72142In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72143In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72144In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72145In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72146In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-72147In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-72141?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
