CVE-2026-90070

tpm: st33zp24: Return zero on status read failure

N/A
Published: September 17, 2026 at 04:05 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

251a7b08213af82e40e4a70cac056e245853c4103.9
Vendor states this is fixed in 14feaa498c20c1b7ddefe27de5329aaff822cc0d (fixed)
Vendor states this is fixed in 1bfd5c54e40704ce93d128a25de3d8dd772bf183 (fixed)
Vendor states this is fixed in 38c26fe4522963a91d4fb02c844d8faa740fe9d1 (fixed)
Vendor states this is fixed in 4973e8386257eed10e5433a94a53bcc6ec37d2a1 (fixed)
Vendor states this is fixed in 8b92687708f5ef980de01c2042dbd76d11f78547 (fixed)
Vendor states this is fixed in 981307e2e8a930da492c2bcf763865c47c2a5165 (fixed)
Vendor states this is fixed in d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42 (fixed)
Vendor states this is fixed in e6d7d9b665419cda3e9f91030d81c9f8ba71e51d (fixed)
Vendor states this is fixed in 3.9 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card