CVE-2026-72151

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt

tpm_buf_append_salt() in drivers/char/tpm/tpm2-sessions.c calls crypto_kpp_generate_public_key() and crypto_kpp_compute_shared_secret() without installing a completion callback, discards both return values, and immediately frees the kpp_request via kpp_request_free(). When the resolved ecdh-nist-p256 KPP backend is asynchronous (atmel-ecc, HPRE, keembay-ocs), either operation returns -EINPROGRESS and the deferred completion worker dereferences the freed request.

The path fires automatically from the hwrng_fillfn kernel thread via tpm_get_random -> tpm2_get_random -> tpm2_start_auth_session -> tpm_buf_append_salt on every entropy poll, without any userland action.

Install crypto_req_done as the completion callback, wrap both KPP operations in crypto_wait_req(), and propagate errors to the caller. The wait is a no-op for synchronous backends.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/934d1cd40e2893bf7a041b54f6afd1c008d7a21c
generic

tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73851a7c43dfa52d2ed9415889b33daf85da0ed9
generic

tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/493333f167926c7adab8e7563e21ad71d8af84fa
generic

tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/111e520efbe82b324bc42b1999b723c0619eea6d

Vendor Advisories for CVE-2026-72151(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 30× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:25 UTCGHSA enrichment
  3. 2026-08-20 09:02 UTCGHSA enrichment
  4. 2026-08-19 20:38 UTCEG score recompute
  5. 2026-08-19 20:38 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 08:14 UTCGHSA enrichment
  8. 2026-08-18 19:50 UTCEG score recompute
  9. 2026-08-18 19:50 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:26 UTCGHSA enrichment
  13. 2026-08-17 19:02 UTCEG score recompute
  14. 2026-08-17 19:01 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:21 UTCEG score recompute
  17. 2026-08-17 06:21 UTCGHSA enrichment
  18. 2026-08-17 06:00 UTCEG score recompute▲ 8.40
  19. 2026-08-17 06:00 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  21. 2026-08-17 05:32 UTCEG score recompute
  22. 2026-08-17 05:32 UTCGHSA enrichment
  23. 2026-08-17 05:24 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 5 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 06:42 UTCGHSA enrichment
  3. 2026-08-15 06:23 UTCNVD update
  4. 2026-08-15 06:11 UTCEG score recompute
  5. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72151?
CVE-2026-72151 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: tpm: tpm2-sessions: wait for async KPP completion in tpmbufappend_salt tpmbufappend_salt() in drivers/char/tpm/tpm2-sessions.c calls cryptokppgeneratepublickey() and cryptokppcomputesharedsecret() without installing a completion…
When was CVE-2026-72151 disclosed?
CVE-2026-72151 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72151 actively exploited?
CVE-2026-72151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72151?
CVE-2026-72151 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-72151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72151

Explore →

Is Your Infrastructure Affected by CVE-2026-72151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs