Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90070tpm: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 4973e8386257eed10e5433a94a53bcc6ec37d2a1
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 981307e2e8a930da492c2bcf763865c47c2a5165
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 1bfd5c54e40704ce93d128a25de3d8dd772bf183
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 38c26fe4522963a91d4fb02c844d8faa740fe9d1
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 14feaa498c20c1b7ddefe27de5329aaff822cc0d
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < e6d7d9b665419cda3e9f91030d81c9f8ba71e51d
    • affected 251a7b08213af82e40e4a70cac056e245853c410 – < 8b92687708f5ef980de01c2042dbd76d11f78547
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90070 badge
[![CVE-2026-90070](https://cveledger.app/badge/CVE-2026-90070.svg)](https://cveledger.app/cve/CVE-2026-90070)

Record last updated .