Answer in brief
CVE-2024-36477 records a Unknown severity vulnerability in tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer. 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 | >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <1547183852dcdfcc25878db7dd3620509217b0cd || >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <de13c56f99477b56980c7e00b09c776d16b7563d || >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <195aba96b854dd664768f382cd1db375d8181f88 | 1547183852dcdfcc25878db7dd3620509217b0cd, de13c56f99477b56980c7e00b09c776d16b7563d, 195aba96b854dd664768f382cd1db375d8181f88 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jun 21, 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: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As such, it does not account for the 4 bytes of header that prepends the SPI data frame. This can result in out-of-bounds accesses and was confirmed with KASAN. Introduce SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-36477 records a Unknown severity vulnerability in tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer. 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 | >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <1547183852dcdfcc25878db7dd3620509217b0cd || >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <de13c56f99477b56980c7e00b09c776d16b7563d || >=a86a42ac2bd652fdc7836a9d880c306a2485c142 <195aba96b854dd664768f382cd1db375d8181f88 | 1547183852dcdfcc25878db7dd3620509217b0cd, de13c56f99477b56980c7e00b09c776d16b7563d, 195aba96b854dd664768f382cd1db375d8181f88 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jun 21, 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: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As such, it does not account for the 4 bytes of header that prepends the SPI data frame. This can result in out-of-bounds accesses and was confirmed with KASAN. Introduce SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.
Quoted source text, attributed separately from HOL analysis.