From: patchwork-bot+netdevbpf@kernel.org
To: Kery Qi <qikeyu2017@gmail.com>
Cc: chandrashekar.devegowda@intel.com, loic.poulain@oss.qualcomm.com,
ryazanov.s.a@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, chiranjeevi.rapolu@linux.intel.com,
haijun.liu@mediatek.com, ricardo.martinez@linux.intel.com,
johannes@sipsolutions.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: wwan: t7xx: fix potential skb->frags overflow in RX path v2
Date: Sun, 25 Jan 2026 22:50:06 +0000 [thread overview]
Message-ID: <176938140610.4002147.1030329011149082820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122170401.1986-2-qikeyu2017@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Jan 2026 01:04:01 +0800 you wrote:
> When receiving data in the DPMAIF RX path,
> the t7xx_dpmaif_set_frag_to_skb() function adds
> page fragments to an skb without checking if the number of
> fragments has exceeded MAX_SKB_FRAGS. This could lead to a buffer overflow
> in skb_shinfo(skb)->frags[] array, corrupting adjacent memory and
> potentially causing kernel crashes or other undefined behavior.
>
> [...]
Here is the summary with links:
- net: wwan: t7xx: fix potential skb->frags overflow in RX path v2
https://git.kernel.org/netdev/net/c/f0813bcd2d9d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-25 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 17:04 [PATCH] net: wwan: t7xx: fix potential skb->frags overflow in RX path v2 Kery Qi
2026-01-25 22:43 ` Jakub Kicinski
2026-01-25 22:50 ` patchwork-bot+netdevbpf [this message]
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=176938140610.4002147.1030329011149082820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qikeyu2017@gmail.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox