| 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-2024-46856: net: phy: dp83822: Fix NULL pointer dereference on DP83825 devices |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: phy: dp83822: Fix NULL pointer dereference on DP83825 devices |
| |
| The probe() function is only used for DP83822 and DP83826 PHY, |
| leaving the private data pointer uninitialized for the DP83825 models |
| which causes a NULL pointer dereference in the recently introduced/changed |
| functions dp8382x_config_init() and dp83822_set_wol(). |
| |
| Add the dp8382x_probe() function, so all PHY models will have a valid |
| private data pointer to fix this issue and also prevent similar issues |
| in the future. |
| |
| The Linux kernel CVE team has assigned CVE-2024-46856 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit 9ef9ecfa9e9f0472adf5b254bda1e0788bc8eaad and fixed in 6.10.11 with commit 67b61e2f4c9c5df97a9a2ef7a1fe35eae00531f4 |
| Issue introduced in 6.10 with commit 9ef9ecfa9e9f0472adf5b254bda1e0788bc8eaad and fixed in 6.11 with commit 3f62ea572b3e8e3f10c39a9cb4f04ca9ae5f2952 |
| |
| 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-2024-46856 |
| 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/phy/dp83822.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/67b61e2f4c9c5df97a9a2ef7a1fe35eae00531f4 |
| https://git.kernel.org/stable/c/3f62ea572b3e8e3f10c39a9cb4f04ca9ae5f2952 |
