| 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-49438: Input: sparcspkr - fix refcount leak in bbc_beep_probe |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| Input: sparcspkr - fix refcount leak in bbc_beep_probe |
| |
| of_find_node_by_path() calls of_find_node_opts_by_path(), |
| which returns a node pointer with refcount |
| incremented, we should use of_node_put() on it when done. |
| Add missing of_node_put() to avoid refcount leak. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49438 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 4.9.318 with commit 2f51db16cb740ff90086189a1ef2581eab665591 |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 4.14.283 with commit f13064b0f2c651a3fbb0749932795c6fd21556a8 |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 4.19.247 with commit 353bc58ac6c782d4dcde9136a91d1f90867938fe |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.4.198 with commit bbc2b0ce6042dd3117827f10ea8cb67e0ab786da |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.10.121 with commit 6e07ccc7d56130f760d23f67a70c45366c07debc |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.15.46 with commit 418b6a3e12f75638abc5673eb76cb32127d0ab13 |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.17.14 with commit 73d6f42d8d86648bec2e73d34fe1648cb6d23e08 |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.18.3 with commit 1124e39fea0e2fdb4202f95b716cb97cc7de7cc7 |
| Issue introduced in 2.6.26 with commit 9c1a5077fdca99356c891af37931e537dea874f5 and fixed in 5.19 with commit c8994b30d71d64d5dcc9bc0edbfdf367171aa96f |
| |
| 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-49438 |
| 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/input/misc/sparcspkr.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/2f51db16cb740ff90086189a1ef2581eab665591 |
| https://git.kernel.org/stable/c/f13064b0f2c651a3fbb0749932795c6fd21556a8 |
| https://git.kernel.org/stable/c/353bc58ac6c782d4dcde9136a91d1f90867938fe |
| https://git.kernel.org/stable/c/bbc2b0ce6042dd3117827f10ea8cb67e0ab786da |
| https://git.kernel.org/stable/c/6e07ccc7d56130f760d23f67a70c45366c07debc |
| https://git.kernel.org/stable/c/418b6a3e12f75638abc5673eb76cb32127d0ab13 |
| https://git.kernel.org/stable/c/73d6f42d8d86648bec2e73d34fe1648cb6d23e08 |
| https://git.kernel.org/stable/c/1124e39fea0e2fdb4202f95b716cb97cc7de7cc7 |
| https://git.kernel.org/stable/c/c8994b30d71d64d5dcc9bc0edbfdf367171aa96f |
