| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53039: HID: intel-ish-hid: ipc: Fix potential use-after-free in work function |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| HID: intel-ish-hid: ipc: Fix potential use-after-free in work function |
| |
| When a reset notify IPC message is received, the ISR schedules a work |
| function and passes the ISHTP device to it via a global pointer |
| ishtp_dev. If ish_probe() fails, the devm-managed device resources |
| including ishtp_dev are freed, but the work is not cancelled, causing a |
| use-after-free when the work function tries to access ishtp_dev. Use |
| devm_work_autocancel() instead, so that the work is automatically |
| cancelled if probe fails. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53039 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.15.105 with commit 8c1d378b8c224fd50247625255f09fc01dcc5836 |
| Fixed in 6.1.22 with commit 0a594cb490ca6232671fc09e2dc1a0fc7ccbb0b5 |
| Fixed in 6.2.9 with commit d3ce3afd9f791dd1b7daedfcf8c396b60af5dec0 |
| Fixed in 6.3 with commit 8ae2f2b0a28416ed2f6d8478ac8b9f7862f36785 |
| |
| 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-2023-53039 |
| 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/hid/intel-ish-hid/ipc/ipc.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/8c1d378b8c224fd50247625255f09fc01dcc5836 |
| https://git.kernel.org/stable/c/0a594cb490ca6232671fc09e2dc1a0fc7ccbb0b5 |
| https://git.kernel.org/stable/c/d3ce3afd9f791dd1b7daedfcf8c396b60af5dec0 |
| https://git.kernel.org/stable/c/8ae2f2b0a28416ed2f6d8478ac8b9f7862f36785 |
