From: patchwork-bot+netdevbpf@kernel.org
To: tobgaertner <tob.gaertner@me.com>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
kuba@kernel.org, gregkh@linuxfoundation.org, oneukum@suse.com,
bjorn@mork.no
Subject: Re: [PATCH v3 0/2] net: usb: cdc_ncm: add ndpoffset to NDP nframes bounds check
Date: Tue, 17 Mar 2026 04:00:09 +0000 [thread overview]
Message-ID: <177372000954.3420008.2772975605346318437.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260314054640.2895026-1-tob.gaertner@me.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 Mar 2026 22:46:38 -0700 you wrote:
> The nframes bounds check in cdc_ncm_rx_verify_ndp16() and
> cdc_ncm_rx_verify_ndp32() does not account for ndpoffset,
> allowing out-of-bounds reads when the NDP is placed near the
> end of the NTB.
>
> Changes since v2:
> - Save struct_size_t() result to a temp variable to avoid
> awkward line wrapping (Jakub)
> - Fix From/Signed-off-by mismatch
> - Move "Compile-tested only" out of the Signed-off-by line
> into the commit message body
>
> [...]
Here is the summary with links:
- [v3,1/2] net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check
https://git.kernel.org/netdev/net/c/2aa8a4fa8d5b
- [v3,2/2] net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check
https://git.kernel.org/netdev/net/c/77914255155e
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-03-17 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 5:46 [PATCH v3 0/2] net: usb: cdc_ncm: add ndpoffset to NDP nframes bounds check tobgaertner
2026-03-14 5:46 ` [PATCH v3 1/2] net: usb: cdc_ncm: add ndpoffset to NDP16 " tobgaertner
2026-03-14 5:46 ` [PATCH v3 2/2] net: usb: cdc_ncm: add ndpoffset to NDP32 " tobgaertner
2026-03-17 4:00 ` 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=177372000954.3420008.2772975605346318437.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=tob.gaertner@me.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