tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s TPM2 session code frees a cryptographic request before an asynchronous KPP operation completes, allowing the completion worker to dereference freed memory. This path runs automatically during entropy polling when an asynchronous ecdh-nist-p256 backend is used; it requires no user action or authentication. The input does not describe a network attack path.
Engineers running Linux kernels with TPM2 sessions and an asynchronous ecdh-nist-p256 KPP backend should check their systems; affected versions were not provided.