From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4655F402444 for ; Tue, 9 Jun 2026 12:11:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781007105; cv=none; b=N9ZFo+xERhGzwomzTH8Xb2ixRFTWeOMm0VsucQmyv+OixhFAC/1zI7Ncap4cAJJdtZeTNBn/pB1B66aDRPXLOtvLU5ekTg382O+dL3ZRbQMEeqIB5Mr6HZQEhYzwGAjLLY6tnHcBZUEcW6od57sbmoui3RyHsB//gEBh/JRKfnY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781007105; c=relaxed/simple; bh=Pv5wr/dP6vGnhWeEdRKtoGhkIOY5w74wWLtPsXtKyQM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=EbO0Ja+nifPFAOSzT3wi6+Zxf1XCsRQsTW9e3VgYtehnLovGAT3aLYLFYw4jo/O9DHL+dU3DS3ERl3AWHeYslVuKBfNGpB+/gNIFuXSyKvFX4R16oBilZTQ0oIzGiZd8GvweF+AK/ld96a3GaXjKzmq/9GgiWRR2jUNGOtkhbec= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=FqWbw6LN; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="FqWbw6LN" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8A9181F00893; Tue, 9 Jun 2026 12:11:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1781007104; bh=fgkKc2FbYnIa4BLotTYD4z1QnUs2tUP6LqyDbSLUMJ4=; h=From:To:Cc:Subject:Date:Reply-To; b=FqWbw6LNSgr94r50/l+nGYrxXRnuEsMy8nX0h7ANm86LAmUfCgNv3oz8sdR+SY+q4 GQnrwcjxe13IPOze8Q8FYziHjbltCyNHL+x2113OqFyXFbuW5TMEwFlgFPsi4ebK37 /qWJDx0slZOOD/SmEsv94921ilosJb/Pwi1P09pQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46323: net: gro: don't merge zcopy skbs Date: Tue, 9 Jun 2026 14:10:29 +0200 Message-ID: <2026060926-CVE-2026-46323-6830@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2919; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JV78H6AobDTm3JHW1+/72Nse5hbsK9/UP3FCuI1suqI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkaTJvmpHxNXFm94sj9G5u1i44Yc/3u9JnqdD/x8+PVT Jcei+4064hlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJrFjCMFdwlbPlGvXMc0xf mKatOyMb76r17h3D/JSiLXvOcv8TOV15Ledogcl757JVAQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net: gro: don't merge zcopy skbs skb_gro_receive() can currently copy frags between the source and GRO skb, without checking the zerocopy status, and in particular the SKBFL_MANAGED_FRAG_REFS flag. When SKBFL_MANAGED_FRAG_REFS is set, the skb doesn't hold a reference on the pages in shinfo->frags. Appending those frags to another skb's frags without fixing up the page refcount can lead to UAF. When either the last skb in the GRO chain (the one we would append frags to) or the source skb is zerocopy, don't merge the skbs. The Linux kernel CVE team has assigned CVE-2026-46323 to this issue. Affected and fixed versions =========================== Issue introduced in 6.0 with commit 753f1ca4e1e50248a1b760c9774d6d6b354562cc and fixed in 6.6.142 with commit 1f9c828556416fbe3f49386708ce999fc4d4da06 Issue introduced in 6.0 with commit 753f1ca4e1e50248a1b760c9774d6d6b354562cc and fixed in 6.12.92 with commit 479084ae0e1d9cb7929cb4298d35623de189f80a Issue introduced in 6.0 with commit 753f1ca4e1e50248a1b760c9774d6d6b354562cc and fixed in 6.18.34 with commit e334cbf3388fd9334503a778a82d9e9f14dd2f71 Issue introduced in 6.0 with commit 753f1ca4e1e50248a1b760c9774d6d6b354562cc and fixed in 7.0.11 with commit 44bea2032af0425e4ce6d26a8af0ede79db49ec1 Issue introduced in 6.0 with commit 753f1ca4e1e50248a1b760c9774d6d6b354562cc and fixed in 7.1-rc5 with commit 4db79a322db8c97f7b73b8a347395ef4d685eb40 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-2026-46323 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: net/core/gro.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/1f9c828556416fbe3f49386708ce999fc4d4da06 https://git.kernel.org/stable/c/479084ae0e1d9cb7929cb4298d35623de189f80a https://git.kernel.org/stable/c/e334cbf3388fd9334503a778a82d9e9f14dd2f71 https://git.kernel.org/stable/c/44bea2032af0425e4ce6d26a8af0ede79db49ec1 https://git.kernel.org/stable/c/4db79a322db8c97f7b73b8a347395ef4d685eb40