From: Hyunwoo Kim <imv4bel@gmail.com>
To: Rajat Gupta <rajat.gupta@oss.qualcomm.com>
Cc: aaron1esau@gmail.com, ben@decadent.org.uk, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com,
herbert@gondor.apana.org.au, horms@kernel.org,
jiayuan.chen@linux.dev, kerneljasonxing@gmail.com,
kuba@kernel.org, kuniyu@google.com, malin89@huawei.com,
mhal@rbox.co, netdev@vger.kernel.org, pabeni@redhat.com,
sd@queasysnail.net, stable@vger.kernel.org,
steffen.klassert@secunet.com, sultan@kerneltoast.com,
tanjingguo@huawei.com, imv4bel@gmail.com
Subject: Re: [PATCH net v5] net: skbuff: propagate shared-frag marker through frag-transfer helpers
Date: Tue, 19 May 2026 15:57:50 +0900 [thread overview]
Message-ID: <agwJ7kbcmJDdLYy6@v4bel> (raw)
In-Reply-To: <agwG_G7l9gdT0BsH@v4bel>
On Tue, May 19, 2026 at 03:45:16PM +0900, Hyunwoo Kim wrote:
> On Mon, May 18, 2026 at 09:02:32PM -0700, Rajat Gupta wrote:
> > The skb_gro_receive() and skb_shift() fixes look correct -- we
> > independently reported both to security@kernel.org with working
>
> Thank you for testing. When did you report it? The two PoCs were
> already public.
>
>
> Best regards,
> Hyunwoo Kim
>
> > LPE exploits confirming they are exploitable from unprivileged
> > user namespaces.
> >
> > Could you add the following tags when respinning or applying?
> >
> > Reported-by: Rajat Gupta <rajat.gupta@oss.qualcomm.com>
These issues have already received many duplicate reports to
security@k.o, and your report was not consulted in the
preparation of this patch.
A Reported-by tag is therefore not appropriate.
Best regards,
Hyunwoo Kim
> > Tested-by: Rajat Gupta <rajat.gupta@oss.qualcomm.com>
>
> >
> > Thanks,
> > Rajat
next prev parent reply other threads:[~2026-05-19 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 22:28 [PATCH net v5] net: skbuff: propagate shared-frag marker through frag-transfer helpers Hyunwoo Kim
2026-05-19 4:02 ` Rajat Gupta
2026-05-19 6:45 ` Hyunwoo Kim
2026-05-19 6:57 ` Hyunwoo Kim [this message]
2026-05-21 9:50 ` patchwork-bot+netdevbpf
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=agwJ7kbcmJDdLYy6@v4bel \
--to=imv4bel@gmail.com \
--cc=aaron1esau@gmail.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=malin89@huawei.com \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rajat.gupta@oss.qualcomm.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=sultan@kerneltoast.com \
--cc=tanjingguo@huawei.com \
/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.