Answer in brief
CVE-2024-42249 records a Unknown severity vulnerability in spi: don't unoptimize message in spi_async(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2 || >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <c86a918b1bdba78fb155184f8d88dfba1e63335d | 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2, c86a918b1bdba78fb155184f8d88dfba1e63335d |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Aug 7, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-42249 records a Unknown severity vulnerability in spi: don't unoptimize message in spi_async(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2 || >=7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 <c86a918b1bdba78fb155184f8d88dfba1e63335d | 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2, c86a918b1bdba78fb155184f8d88dfba1e63335d |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Aug 7, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.