| 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: <2025050225-CVE-2023-53104-d632@gregkh> Date: Fri, 2 May 2025 17:56:09 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53104: net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull Packet length check needs to be located after size and align_count calculation to prevent kernel panic in skb_pull() in case rx_cmd_a & RX_CMD_A_RED evaluates to true. The Linux kernel CVE team has assigned CVE-2023-53104 to this issue. Affected and fixed versions =========================== Issue fixed in mainline with commit 43ffe6c 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-53104 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/usb/smsc75xx.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/5c96eeba93980c5cef5176a4bac0ddb722fd57dc https://git.kernel.org/stable/c/89441504d66d116eb5ce58c132f58cdcca5b498a https://git.kernel.org/stable/c/e0d07a3203c36d073af2177edfc6b070220a60cb https://git.kernel.org/stable/c/2cc46ed406bb325f10a251b03d9a83ae67b3d3d8 https://git.kernel.org/stable/c/7bf0eac3fdd2d25f5c6ceab63e3e4902e274f7ee https://git.kernel.org/stable/c/4caee8e7d91e4f06f21881726da9c1bb2cd6e4fa https://git.kernel.org/stable/c/181e9db5caec4daae57a58675a1ceaa47348958f https://git.kernel.org/stable/c/43ffe6caccc7a1bb9d7442fbab521efbf6c1378c
Powered by blists - more mailing lists