{"id":"CVE-2026-72141","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-72141","generatedAt":"2026-10-28T07:25:17.124Z","title":"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.","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: imx: fix locked bus on SMBus block-read of 0 (IRQ)\n\nSMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the\ninterrupt-driven block-read state machine rejects it as -EPROTO. Worse,\nit returns without a NACK+STOP: the next receive cycle has already\nstarted, so the target keeps holding SDA and the bus stays stuck until a\npower cycle of this i2c controller.\n\nAccept count=0: NACK the in-flight dummy byte (TXAK) and set msg->len to\n2 so i2c_imx_isr_read_continue() emits STOP via its normal last-byte\npath. The dummy byte is discarded; block-read callers only consume\nbuf[0..count-1].\n\nReading I2DR has likewise already armed the next byte on the\ncount > I2C_SMBUS_BLOCK_MAX error path, so NACK it (TXAK) before aborting\nwith -EPROTO; otherwise the failing transfer's STOP cannot complete and\nthe bus stays held.\n\nThe atomic path regressed earlier (v3.16) and is fixed separately; this\npatch covers only the v6.13 state-machine rework.","published":"2026-08-15T06:21:32.000Z","lastModified":"2026-08-17T06:18:14.000Z","status":"Received","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","cvss":{"version":"3.1","score":7.5,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"},"cwe":[],"affected":[],"epss":{"score":0.00609,"percentile":0.48955,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.61%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://git.kernel.org/stable/c/07fd9385f0d87dff4b34f355f68adf701080cb24","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/56ddfc18ea8f7d77747658892873eb632b2ed530","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/5d3240f42a667e29262aff76fdebfcdac4980626","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72141","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}