| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49286: tpm: use try_get_ops() in tpm-space.c |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tpm: use try_get_ops() in tpm-space.c |
| |
| As part of the series conversion to remove nested TPM operations: |
| |
| https://lore.kernel.org/all/20190205224723.19671-1-jarkko.sakkinen@linux.intel.com/ |
| |
| exposure of the chip->tpm_mutex was removed from much of the upper |
| level code. In this conversion, tpm2_del_space() was missed. This |
| didn't matter much because it's usually called closely after a |
| converted operation, so there's only a very tiny race window where the |
| chip can be removed before the space flushing is done which causes a |
| NULL deref on the mutex. However, there are reports of this window |
| being hit in practice, so fix this by converting tpm2_del_space() to |
| use tpm_try_get_ops(), which performs all the teardown checks before |
| acquring the mutex. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49286 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.4.188 with commit 5b1d2561a03e534064b51c50c774657833d3d2cf |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.10.109 with commit 95193d12f10a8a088843b25e0f5fe1d83ec6b079 |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.15.32 with commit 476ddd23f818fb94cf86fb5617f3bb9a7c92113d |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.16.18 with commit eda1662cce964c8a65bb86321f8d9cfa6e9ceaab |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.17.1 with commit ba84f9a48366dcc3cdef978599433efe101dd5bd |
| Issue introduced in 4.12 with commit 745b361e989af21ad40811c2586b60229f870a68 and fixed in 5.18 with commit fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2022-49286 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/char/tpm/tpm2-space.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/5b1d2561a03e534064b51c50c774657833d3d2cf |
| https://git.kernel.org/stable/c/95193d12f10a8a088843b25e0f5fe1d83ec6b079 |
| https://git.kernel.org/stable/c/476ddd23f818fb94cf86fb5617f3bb9a7c92113d |
| https://git.kernel.org/stable/c/eda1662cce964c8a65bb86321f8d9cfa6e9ceaab |
| https://git.kernel.org/stable/c/ba84f9a48366dcc3cdef978599433efe101dd5bd |
| https://git.kernel.org/stable/c/fb5abce6b2bb5cb3d628aaa63fa821da8c4600f9 |
