0.0
NA
CVE-2026-90070
tpm: st33zp24: Return zero on status read failure
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.

INFO

Published Date :

Sept. 17, 2026, 5:16 p.m.

Last Modified :

Sept. 17, 2026, 5:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-90070 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Address potential data misinterpretation due to I2C transport failures by returning zero on status read failure.
  • Ensure status reads return zero on transport failure.
  • Verify only one byte is received before processing status.
  • Update the Linux kernel to include the fix.
  • Rely on existing timeouts or error paths for failures.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-90070 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-90070 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-90070 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-90070 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 17, 2026

    Action Type Old Value New Value
    Added 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.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/90xxx/CVE-2026-90070.json">CVE-2026-90070</a>
    Added Reference https://git.kernel.org/stable/c/14feaa498c20c1b7ddefe27de5329aaff822cc0d
    Added Reference https://git.kernel.org/stable/c/1bfd5c54e40704ce93d128a25de3d8dd772bf183
    Added Reference https://git.kernel.org/stable/c/38c26fe4522963a91d4fb02c844d8faa740fe9d1
    Added Reference https://git.kernel.org/stable/c/4973e8386257eed10e5433a94a53bcc6ec37d2a1
    Added Reference https://git.kernel.org/stable/c/8b92687708f5ef980de01c2042dbd76d11f78547
    Added Reference https://git.kernel.org/stable/c/981307e2e8a930da492c2bcf763865c47c2a5165
    Added Reference https://git.kernel.org/stable/c/d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42
    Added Reference https://git.kernel.org/stable/c/e6d7d9b665419cda3e9f91030d81c9f8ba71e51d
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.