ieee802154: ca8210: fix cas_ctl leak on spi_async failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fe90605b651573d30be8293ff5be40e3d7023117, Kernel 460c5cd51e4d7d15b317f178f42cfcb666c0fe91, Kernel 7e3630fbb6aabb844bbf35746dee0bf3894100c7 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: ieee802154: ca8210: fix cas_ctl leak on spi_async failure ca8210_spi_transfer() allocates cas_ctl with kzalloc_obj(GFP_ATOMIC) and relies entirely on the SPI completion callback ca8210_spi_transfer_complete() to free it. The spi_async() API only invokes the completion callback on successful submission. On failure it returns a negative error code without ever queuing the callback, which leaves cas_ctl and its embedded spi_message and spi_transfer orphaned. Every kfree(cas_ctl) in the driver is inside the completion callback, so there is no other reclamation path. ca8210_spi_transfer() is called from ca8210_spi_exchange(), the interrupt handler ca8210_interrupt_handler(), and from the retry path inside the completion callback itself. The exchange and interrupt handler paths loop on -EBUSY, so under sustained SPI bus contention every retry iteration leaks a fresh cas_ctl (~600 bytes per occurrence). Fix it by freeing cas_ctl on the spi_async() error path. While here, correct the misleading error string: the function calls spi_async(), not spi_sync().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <fe90605b651573d30be8293ff5be40e3d7023117, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <460c5cd51e4d7d15b317f178f42cfcb666c0fe91, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <7e3630fbb6aabb844bbf35746dee0bf3894100c7, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <b07aea90dbc6e188c74c100af64b77b9482ffc65, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <b9071dc7889bef42590e04fbf3e56cc65e1e5e6e, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <cb5cca1d2a908ddd5e357971de0f2009617b8d6a, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <d4a397fe803c2d157f6ebb068b802ef75fbf109e, >=ded845a781a578dfb0b5b2c138e5a067aa3b1242 <e09390e439bd7cca30dd10893b1f64802961667a, =4.12 | fe90605b651573d30be8293ff5be40e3d7023117, 460c5cd51e4d7d15b317f178f42cfcb666c0fe91, 7e3630fbb6aabb844bbf35746dee0bf3894100c7, b07aea90dbc6e188c74c100af64b77b9482ffc65, b9071dc7889bef42590e04fbf3e56cc65e1e5e6e, cb5cca1d2a908ddd5e357971de0f2009617b8d6a, d4a397fe803c2d157f6ebb068b802ef75fbf109e, e09390e439bd7cca30dd10893b1f64802961667a |
| linux-kernel: Kernel | >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=4.12.0 <5.10.261 | 5.15.212, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.261 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket