CVE-2026-90070 — tpm: st33zp24: Return zero on status read failure
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 251a7b08213af82e40e4a70cac056e245853c410 and < d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 4973e8386257eed10e5433a94a53bcc6ec37d2a1≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 981307e2e8a930da492c2bcf763865c47c2a5165≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 1bfd5c54e40704ce93d128a25de3d8dd772bf183≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 38c26fe4522963a91d4fb02c844d8faa740fe9d1≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 14feaa498c20c1b7ddefe27de5329aaff822cc0d≥ 251a7b08213af82e40e4a70cac056e245853c410 and < e6d7d9b665419cda3e9f91030d81c9f8ba71e51d≥ 251a7b08213af82e40e4a70cac056e245853c410 and < 8b92687708f5ef980de01c2042dbd76d11f78547 and 1 moreversion 3.9 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/8b92687708f5ef980de01c2042dbd76d11f78547
- git.kernel.org/stable/c/981307e2e8a930da492c2bcf763865c47c2a5165
- nvd.nist.gov/vuln/detail/CVE-2026-90070
- git.kernel.org/stable/c/1bfd5c54e40704ce93d128a25de3d8dd772bf183
- git.kernel.org/stable/c/e6d7d9b665419cda3e9f91030d81c9f8ba71e51d
- git.kernel.org/stable/c/14feaa498c20c1b7ddefe27de5329aaff822cc0d
- git.kernel.org/stable/c/4973e8386257eed10e5433a94a53bcc6ec37d2a1
- github.com/advisories/GHSA-q7v7-xw33-v766
- git.kernel.org/stable/c/d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42
- git.kernel.org/stable/c/38c26fe4522963a91d4fb02c844d8faa740fe9d1
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90070 is "tpm: st33zp24: Return zero on status read failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.