| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025121643-CVE-2025-68302-913d@gregkh> Date: Tue, 16 Dec 2025 16:06:56 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-68302: net: sxgbe: fix potential NULL dereference in sxgbe_rx() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is null, the driver prints an error and then dereferences skb on the next line. To fix this, let's add a 'break' after the error message to switch to sxgbe_rx_refill(), which is similar to the approach taken by the other drivers in this particular case, e.g. calxeda with xgmac_rx(). Found during a code review. The Linux kernel CVE team has assigned CVE-2025-68302 to this issue. Affected and fixed versions =========================== Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 5.10.247 with commit ac171c3c755499c9f87fe30b920602255f8b5648 Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 5.15.197 with commit 18ef3ad1bb57dcf1a9ee61736039aedccf670b21 Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.1.159 with commit 46e5332126596a2ca791140feab18ce1fc1a3c86 Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.6.119 with commit 7fd789d6ea4915034eb6bcb72f6883c8151083e5 Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.12.61 with commit 45b5b4ddb8d6bea5fc1625ff6f163bbb125d49cc Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.17.11 with commit 88f46c0be77bfe45830ac33102c75be7c34ac3f3 Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.18 with commit f5bce28f6b9125502abec4a67d68eabcd24b3b17 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-2025-68302 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/ethernet/samsung/sxgbe/sxgbe_main.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/ac171c3c755499c9f87fe30b920602255f8b5648 https://git.kernel.org/stable/c/18ef3ad1bb57dcf1a9ee61736039aedccf670b21 https://git.kernel.org/stable/c/46e5332126596a2ca791140feab18ce1fc1a3c86 https://git.kernel.org/stable/c/7fd789d6ea4915034eb6bcb72f6883c8151083e5 https://git.kernel.org/stable/c/45b5b4ddb8d6bea5fc1625ff6f163bbb125d49cc https://git.kernel.org/stable/c/88f46c0be77bfe45830ac33102c75be7c34ac3f3 https://git.kernel.org/stable/c/f5bce28f6b9125502abec4a67d68eabcd24b3b17
Powered by blists - more mailing lists