spi: don't unoptimize message in spi_async()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2 and Kernel c86a918b1bdba78fb155184f8d88dfba1e63335d.
In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver. spi_maybe_unoptimize_message() is already called in the correct place in spi_finalize_current_message() to balance the call to spi_maybe_optimize_message() in spi_async().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2, >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <c86a918b1bdba78fb155184f8d88dfba1e63335d | 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2, c86a918b1bdba78fb155184f8d88dfba1e63335d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket