Answer in brief
CVE-2026-72151 records a Unknown severity vulnerability in tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <111e520efbe82b324bc42b1999b723c0619eea6d || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <934d1cd40e2893bf7a041b54f6afd1c008d7a21c || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <493333f167926c7adab8e7563e21ad71d8af84fa || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <73851a7c43dfa52d2ed9415889b33daf85da0ed9 | 111e520efbe82b324bc42b1999b723c0619eea6d, 934d1cd40e2893bf7a041b54f6afd1c008d7a21c, 493333f167926c7adab8e7563e21ad71d8af84fa, 73851a7c43dfa52d2ed9415889b33daf85da0ed9 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72151 records a Unknown severity vulnerability in tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <111e520efbe82b324bc42b1999b723c0619eea6d || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <934d1cd40e2893bf7a041b54f6afd1c008d7a21c || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <493333f167926c7adab8e7563e21ad71d8af84fa || >=1085b8276bb4239daa7008f0dcd5c973e4bd690f <73851a7c43dfa52d2ed9415889b33daf85da0ed9 | 111e520efbe82b324bc42b1999b723c0619eea6d, 934d1cd40e2893bf7a041b54f6afd1c008d7a21c, 493333f167926c7adab8e7563e21ad71d8af84fa, 73851a7c43dfa52d2ed9415889b33daf85da0ed9 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.