From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46323: net: gro: don't merge zcopy skbs
Date: Tue, 9 Jun 2026 14:10:29 +0200 [thread overview]
Message-ID: <2026060926-CVE-2026-46323-6830@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-06-09 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026060926-CVE-2026-46323-6830@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.