| 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-53092: interconnect: exynos: fix node leak in probe PM QoS error path |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| interconnect: exynos: fix node leak in probe PM QoS error path |
| |
| Make sure to add the newly allocated interconnect node to the provider |
| before adding the PM QoS request so that the node is freed on errors. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53092 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.11 with commit 2f95b9d5cf0b3d15154225e369558a3c6b40e948 and fixed in 5.15.104 with commit fd4738ae1a0c216d25360a98e835967b06d6a253 |
| Issue introduced in 5.11 with commit 2f95b9d5cf0b3d15154225e369558a3c6b40e948 and fixed in 6.1.21 with commit c479e4ac4a3d1485a48599e66ce46547c1367828 |
| Issue introduced in 5.11 with commit 2f95b9d5cf0b3d15154225e369558a3c6b40e948 and fixed in 6.2.8 with commit b71dd43bd49bd68186c1d19dbeedee219e003149 |
| Issue introduced in 5.11 with commit 2f95b9d5cf0b3d15154225e369558a3c6b40e948 and fixed in 6.3 with commit 3aab264875bf3c915ea2517fae1eec213e0b4987 |
| |
| 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-53092 |
| 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/interconnect/samsung/exynos.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/fd4738ae1a0c216d25360a98e835967b06d6a253 |
| https://git.kernel.org/stable/c/c479e4ac4a3d1485a48599e66ce46547c1367828 |
| https://git.kernel.org/stable/c/b71dd43bd49bd68186c1d19dbeedee219e003149 |
| https://git.kernel.org/stable/c/3aab264875bf3c915ea2517fae1eec213e0b4987 |
