| 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-49367: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register |
| |
| of_get_child_by_name() returns a node pointer with refcount |
| incremented, we should use of_node_put() on it when done. |
| |
| mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). |
| We don't need the device node after it. |
| |
| Add missing of_node_put() to avoid refcount leak. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49367 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 4.14.283 with commit dc1cf8c6f9793546696fded437a5b4c84944c48b |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 4.19.247 with commit 86c3c5f8e4bd1325e24f6fba9017cade29933377 |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.4.198 with commit a101793994c0a14c70bb4e44c7fda597eeebba0a |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.10.122 with commit 42658e47f1abbbe592007d3ba303de466114d0bb |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.15.47 with commit c1df9cb756e5a9ba1841648c44ee5d92306b9c65 |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.17.15 with commit e0d763d0c7665c7897e4f5a0847ab0c82543345f |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.18.4 with commit 8a1a1255152da4fb934290e7ababc66f24985520 |
| Issue introduced in 4.11 with commit a3c53be55c955b7150cda17874c3fcb4eeb97a89 and fixed in 5.19 with commit 02ded5a173619b11728b8bf75a3fd995a2c1ff28 |
| |
| 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-49367 |
| 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/net/dsa/mv88e6xxx/chip.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/dc1cf8c6f9793546696fded437a5b4c84944c48b |
| https://git.kernel.org/stable/c/86c3c5f8e4bd1325e24f6fba9017cade29933377 |
| https://git.kernel.org/stable/c/a101793994c0a14c70bb4e44c7fda597eeebba0a |
| https://git.kernel.org/stable/c/42658e47f1abbbe592007d3ba303de466114d0bb |
| https://git.kernel.org/stable/c/c1df9cb756e5a9ba1841648c44ee5d92306b9c65 |
| https://git.kernel.org/stable/c/e0d763d0c7665c7897e4f5a0847ab0c82543345f |
| https://git.kernel.org/stable/c/8a1a1255152da4fb934290e7ababc66f24985520 |
| https://git.kernel.org/stable/c/02ded5a173619b11728b8bf75a3fd995a2c1ff28 |
