![⚡ THN Weekly Recap: Top Cybersecurity Threats, Tools and Tips [30 Dec]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfYK_dlQo9n6UQiuexPS4b1dZ039bN14TXB6AswBkkoRAzzAJg7N3ihBHLhefti8RGcxX6HNI0wVhF8dHLT29WcL2UIUv2n81OsQEbYGKSV6N4aJR-OaK9cV0rWfJWElVsPsjjWvNfb0ZfkRgYfXWIbDBj14YS5VvaBSf7ke5iqzAL2DF7C3IGZRMMwdaf/s1600/recap.png?#)
CVE-2024-42249 - Linux Kernel SPI Corrupting Message Vulnerability
CVE ID : CVE-2024-42249 Published : Aug. 7, 2024, 4:15 p.m. | 1 hour, 14 minutes ago Description : 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(). Severity: 0.0 | NA Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE ID : CVE-2024-42249
Published : Aug. 7, 2024, 4:15 p.m. | 1 hour, 14 minutes ago
Description : 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().
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
Published : Aug. 7, 2024, 4:15 p.m. | 1 hour, 14 minutes ago
Description : 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().
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
