| 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-48782: mctp: fix use after free |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| mctp: fix use after free |
| |
| Clang static analysis reports this problem |
| route.c:425:4: warning: Use of memory after it is freed |
| trace_mctp_key_acquire(key); |
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| When mctp_key_add() fails, key is freed but then is later |
| used in trace_mctp_key_acquire(). Add an else statement |
| to use the key only when mctp_key_add() is successful. |
| |
| The Linux kernel CVE team has assigned CVE-2022-48782 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.16 with commit 4f9e1ba6de45aa8797a83f1fe5b82ec4bac16899 and fixed in 5.16.11 with commit 1dd3ecbec5f606b2a526c47925c8634b1a6bb81e |
| Issue introduced in 5.16 with commit 4f9e1ba6de45aa8797a83f1fe5b82ec4bac16899 and fixed in 5.17 with commit 7e5b6a5c8c44310784c88c1c198dde79f6402f7b |
| |
| 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-48782 |
| 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: |
| net/mctp/route.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/1dd3ecbec5f606b2a526c47925c8634b1a6bb81e |
| https://git.kernel.org/stable/c/7e5b6a5c8c44310784c88c1c198dde79f6402f7b |
