From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: rivaldihormat-debug <rivaldihormat@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: core: devio: add defensive bounds check for len2 in do_proc_bulk()
Date: Fri, 4 Sep 2026 08:47:42 +0200 [thread overview]
Message-ID: <2026090433-repayment-duplicate-bb50@gregkh> (raw)
In-Reply-To: <20260904063918.21213-2-rivaldihormat@gmail.com>
On Fri, Sep 04, 2026 at 06:39:18AM +0000, rivaldihormat-debug wrote:
> Although the USB host controller hardware prevents len2 from exceeding
> len1 in normal operation via babble error handling, add an explicit
> kernel-side check to improve robustness. This helps prevent unexpected
> behavior in virtualized environments where emulation bugs might break
> this guarantee.
>
> Clamp len2 to len1 if it exceeds the allocated buffer size and log
> a warning message.
>
> Signed-off-by: rivaldihormat-debug <rivaldihormat@gmail.com>
> ---
> .../net/ethernet/intel/i40e/i40e_debugfs.c | 1855 +++++++++++++++++
> 1 file changed, 1855 insertions(+)
> create mode 100644 linux-6.6/drivers/net/ethernet/intel/i40e/i40e_debugfs.c
Something went really wrong with this patch :(
next prev parent reply other threads:[~2026-09-04 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 6:39 [PATCH] i40e: fix integer overflow in i40e_dbg_command_write() rivaldihormat-debug
2026-09-04 6:39 ` [PATCH] usb: core: devio: add defensive bounds check for len2 in do_proc_bulk() rivaldihormat-debug
2026-09-04 6:47 ` Greg Kroah-Hartman [this message]
2026-09-04 6:47 ` [PATCH] i40e: fix integer overflow in i40e_dbg_command_write() Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2026-09-04 6:29 [PATCH] usb: core: devio: add defensive bounds check for len2 in do_proc_bulk() rivaldihormat-debug
2026-09-04 6:48 ` Greg Kroah-Hartman
2026-09-04 16:37 ` Alan Stern
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=2026090433-repayment-duplicate-bb50@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=rivaldihormat@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