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 5043F490BE1 for ; Fri, 25 Sep 2026 10:26:27 +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=1790331988; cv=none; b=t7mAHcuc9f6l8coyiXHRHYHzyYMc1uTFCpgxZQiUof8nX/cfBaPckqgsLBsUZOP+kyaA1WZ6LUrw9aCozswp5WlCtftVoN3VqSXSsqutBlD8ZIWWyLJTmOOYH8yfzV8Op15vL/fsKObDzJjaw6ew6PqHEvWK865B0RbTAK+9QgQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790331988; c=relaxed/simple; bh=33rOZhRK88rzuO0jNcUpAS2tWrQSDNBFDyF07ZkRkas=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=oe9rnhUhWwo0UTE78OyuFn6VuWA3WFLH9zOZ/hRvSZsK4iDD3KY20DA1S4fUbLu++gbjz02TjndZnnPLFsqFdQG9VJ7ruNM56MciBRitgKnjq+7jSoHNpH54+0iBZb9cmxLjPlIf9jty3vLk724/PVdynLTLvIchw3xaKnY7JsM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=wmIrAltr; 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="wmIrAltr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A708F1F000FF; Fri, 25 Sep 2026 10:26:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790331987; bh=rAOKP2/pZO4BDJOZZZsKviG8f62BAVqdVOAfNbn/PF0=; h=From:To:Cc:Subject:Date:Reply-To; b=wmIrAltr9KCX13RkuPzzWFwOxOSPV36lw/jx2tGJ9Szg/GtPyNh6c0cBCIwkxS6/Y m7fdVFg4cBoU3X/0ZvTkeu5+pHTy3HCseO9WNqBHWECua/5tKbBRVrFjVQNoeH2hDC HiGHjaIorIYSggBfARt6BBc/xfwzPj0fAaZ+2Q3g= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-97602: inet: frags: invalidate queues before flushing them Date: Fri, 25 Sep 2026 12:23:02 +0200 Message-ID: <2026092500-CVE-2026-97602-6089@gregkh> X-Mailer: git-send-email 2.55.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=6122; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=luQKXZJ4NP+h+yTSwgxzbYBXCVEHGmPukQdkcfjnqiM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnbvD22aMonVGVq/zzSvi/9TvykWfOCCmTYrvxx7bOa5 bdj33mljlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjI8gCGBdvZ71leShIyctl6 hsF6oczOHQec3Bnmh5zaEOmtvSbSqjLFX/Bjy2kPwQ33AQ== 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: inet: frags: invalidate queues before flushing them fqdir_pre_exit() flushes the skbs from incomplete queues without changing their completion state. A fragment which found a queue before high_thresh was cleared can then acquire the queue lock and reuse stale reassembly metadata. A queue concurrently killed after fqdir->dead is set can instead become INET_FRAG_COMPLETE|INET_FRAG_HASH_DEAD while still holding its old skbs; skipping it because it is complete leaves those references behind until asynchronous fqdir teardown. For IPv6, stale metadata can make ip6_frag_reasm() use the old nhoffset with a new skb and access memory out of bounds. The resulting heap corruption can be leveraged for local privilege escalation when unprivileged network namespaces are available. Unflushed fragments can also keep conntrack references alive after the conntrack per-net cleanup point. Kill each incomplete queue, then flush every queue still owned by the dying rhashtable. HASH_DEAD identifies that ownership, while complete queues without it are already owned by another destroy path and must be left alone. Releasing a timer reference removed by inet_frag_kill() is deferred to inet_frag_putn(), after the queue lock is dropped. KASAN report: BUG: KASAN: slab-out-of-bounds in ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) Write of size 1 at addr ff110001039c6e00 by task poc/771 Call Trace: ? ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) ipv6_frag_rcv (net/ipv6/reassembly.c:289 (discriminator 2) net/ipv6/reassembly.c:229 (discriminator 2) net/ipv6/reassembly.c:391 (discriminator 2)) ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479 (discriminator 5)) ip6_input_finish (net/ipv6/ip6_input.c:534) ipv6_rcv (include/net/dst.h:480 (discriminator 3) net/ipv6/ip6_input.c:119 (discriminator 3) net/ipv6/ip6_input.c:109 (discriminator 3) include/linux/netfilter.h:325 (discriminator 3) include/linux/netfilter.h:319 (discriminator 3) net/ipv6/ip6_input.c:351 (discriminator 3)) packet_sendmsg (net/packet/af_packet.c:3110 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) The buggy address belongs to the object at ff110001039c6b40 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 0 bytes to the right of allocated 704-byte region [ff110001039c6b40, ff110001039c6e00) BUG: KASAN: slab-out-of-bounds in ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) Read of size 1 at addr ff110001039c6e08 by task poc/771 Call Trace: ? ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:423 (discriminator 1)) ip6_input_finish (net/ipv6/ip6_input.c:534) ipv6_rcv (include/net/dst.h:480 (discriminator 3) net/ipv6/ip6_input.c:119 (discriminator 3) net/ipv6/ip6_input.c:109 (discriminator 3) include/linux/netfilter.h:325 (discriminator 3) include/linux/netfilter.h:319 (discriminator 3) net/ipv6/ip6_input.c:351 (discriminator 3)) packet_sendmsg (net/packet/af_packet.c:3110 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) packet_sendmsg (net/packet/af_packet.c:2959 net/packet/af_packet.c:3053 net/packet/af_packet.c:3142) __x64_sys_sendmmsg (net/socket.c:2883 net/socket.c:2880 net/socket.c:2880) The buggy address belongs to the object at ff110001039c6b40 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 8 bytes to the right of allocated 704-byte region [ff110001039c6b40, ff110001039c6e00) The Linux kernel CVE team has assigned CVE-2026-97602 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12.93 with commit 543555954b1ee8d1903a7020324efb41b0c97428 and fixed in 6.12.111 with commit b9d77f1652e79e58eac48430d0431c329137efcc Issue introduced in 6.18.3 with commit c70df25214ac9b32b53e18e6ae3b8f073ffa6903 and fixed in 6.18.53 with commit 7cb5f4643a7fcdbfbee1fad3cdfc678add62d378 Issue introduced in 6.19 with commit 006a5035b495dec008805df249f92c22c89c3d2e and fixed in 7.2.7 with commit bf3d6c44c84c57e8a4bb7f40ad95b64f9b0198ba Issue introduced in 6.19 with commit 006a5035b495dec008805df249f92c22c89c3d2e and fixed in 7.3-rc3 with commit b824476c56a153934c67c9e0f873e1fd967743d6 Issue introduced in 6.6.143 with commit 22ee4010866da81aeee08e1ea3fddbe418feb212 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-97602 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/ipv4/inet_fragment.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/b9d77f1652e79e58eac48430d0431c329137efcc https://git.kernel.org/stable/c/7cb5f4643a7fcdbfbee1fad3cdfc678add62d378 https://git.kernel.org/stable/c/bf3d6c44c84c57e8a4bb7f40ad95b64f9b0198ba https://git.kernel.org/stable/c/b824476c56a153934c67c9e0f873e1fd967743d6