Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 14feaa498c20c1b7ddefe27de5329aaff822cc0d, 1bfd5c54e40704ce93d128a25de3d8dd772bf183, 38c26fe4522963a91d4fb02c844d8faa740fe9d1.

Low priority for now. Upgrade to Linux Linux 14feaa498c20c1b7ddefe27de5329aaff822cc0d, 1bfd5c54e40704ce93d128a25de3d8dd772bf183, 38c26fe4522963a91d4fb02c844d8faa740fe9d1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90070

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.9affected
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42affected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 4973e8386257eed10e5433a94a53bcc6ec37d2a1affected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 981307e2e8a930da492c2bcf763865c47c2a5165affected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 1bfd5c54e40704ce93d128a25de3d8dd772bf183affected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 38c26fe4522963a91d4fb02c844d8faa740fe9d1affected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 14feaa498c20c1b7ddefe27de5329aaff822cc0daffected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before e6d7d9b665419cda3e9f91030d81c9f8ba71e51daffected · git
    • 251a7b08213af82e40e4a70cac056e245853c410 and later · before 8b92687708f5ef980de01c2042dbd76d11f78547affected · git
    • before 3.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90068Sep 17, 2026 · ASoC: dapm: Fix off-by-one check on the second enum channel
    0Monitor
  • ← EarlierCVE-2026-90069Sep 17, 2026 · crypto: acomp - allocate async request context when cloning
    31Monitor
  • Later →CVE-2026-90071Sep 17, 2026 · net/sched: sch_teql: restore skb->dev on the slave failure path
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux14feaa498c20c1b7ddefe27de5329aaff822cc0dVendor (CNA)
Linux Linux1bfd5c54e40704ce93d128a25de3d8dd772bf183Vendor (CNA)
Linux Linux38c26fe4522963a91d4fb02c844d8faa740fe9d1Vendor (CNA)
Linux Linux4973e8386257eed10e5433a94a53bcc6ec37d2a1Vendor (CNA)
Linux Linux8b92687708f5ef980de01c2042dbd76d11f78547Vendor (CNA)
Linux Linux981307e2e8a930da492c2bcf763865c47c2a5165Vendor (CNA)
Linux Linuxd732cfc4befe28f02ec82ed5fd2bc2a21fbabd42Vendor (CNA)
Linux Linuxe6d7d9b665419cda3e9f91030d81c9f8ba71e51dVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records