| 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: <2025071033-CVE-2025-38331-aad6@gregkh> Date: Thu, 10 Jul 2025 10:15:39 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38331: net: ethernet: cortina: Use TOE/TSO on all TCP From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: net: ethernet: cortina: Use TOE/TSO on all TCP It is desireable to push the hardware accelerator to also process non-segmented TCP frames: we pass the skb->len to the "TOE/TSO" offloader and it will handle them. Without this quirk the driver becomes unstable and lock up and and crash. I do not know exactly why, but it is probably due to the TOE (TCP offload engine) feature that is coupled with the segmentation feature - it is not possible to turn one part off and not the other, either both TOE and TSO are active, or neither of them. Not having the TOE part active seems detrimental, as if that hardware feature is not really supposed to be turned off. The datasheet says: "Based on packet parsing and TCP connection/NAT table lookup results, the NetEngine puts the packets belonging to the same TCP connection to the same queue for the software to process. The NetEngine puts incoming packets to the buffer or series of buffers for a jumbo packet. With this hardware acceleration, IP/TCP header parsing, checksum validation and connection lookup are offloaded from the software processing." After numerous tests with the hardware locking up after something between minutes and hours depending on load using iperf3 I have concluded this is necessary to stabilize the hardware. The Linux kernel CVE team has assigned CVE-2025-38331 to this issue. Affected and fixed versions =========================== Fixed in 6.1.142 with commit 1b503b790109d19710ec83c589c3ee59e95347ec Fixed in 6.6.95 with commit a37888a435b0737128d2d9c6f67b8d608f83df7a Fixed in 6.12.35 with commit 2bd434bb0eeb680c2b3dd6c68ca319b30cb8d47f Fixed in 6.15.4 with commit ebe12e232f1d58ebb4b53b6d9149962b707bed91 Fixed in 6.16-rc1 with commit 6a07e3af4973402fa199a80036c10060b922c92c 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-38331 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/cortina/gemini.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/1b503b790109d19710ec83c589c3ee59e95347ec https://git.kernel.org/stable/c/a37888a435b0737128d2d9c6f67b8d608f83df7a https://git.kernel.org/stable/c/2bd434bb0eeb680c2b3dd6c68ca319b30cb8d47f https://git.kernel.org/stable/c/ebe12e232f1d58ebb4b53b6d9149962b707bed91 https://git.kernel.org/stable/c/6a07e3af4973402fa199a80036c10060b922c92c
Powered by blists - more mailing lists