i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e3e8b02d4773cfc5ad561d2e5505efde36c6927a, Kernel 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3, Kernel 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <e3e8b02d4773cfc5ad561d2e5505efde36c6927a, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <016ef0f6ca4bc9bf0330ac41bd2ea349759643e3, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <38d4947431b2410850409fda016b2ac9f640a4dd, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <60ed00d46616a9232e42ea7a3e3c0273d7cf7543, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <6d2c973926d0612360693bc559be2ffde836151b, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <c882e8cc68fb993700dc21fd6e754001e6297934, >=8e8782c71595a5ad29e234ce6b3d2fce787fb07a <cb2fc37857693b55909fb77dc2c87cfbc1cdc476, =3.16 | e3e8b02d4773cfc5ad561d2e5505efde36c6927a, 016ef0f6ca4bc9bf0330ac41bd2ea349759643e3, 0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec, 38d4947431b2410850409fda016b2ac9f640a4dd, 60ed00d46616a9232e42ea7a3e3c0273d7cf7543, 6d2c973926d0612360693bc559be2ffde836151b, c882e8cc68fb993700dc21fd6e754001e6297934, cb2fc37857693b55909fb77dc2c87cfbc1cdc476 |
| linux-kernel: Kernel | >=5.11.0 <5.15.217, >=5.16.0 <6.1.184, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=3.16.0 <5.10.266 | 5.15.217, 6.1.184, 6.18.40, 7.1.5, 6.6.148, 6.12.101, 5.10.266 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket