From: Simon Horman <horms@kernel.org>
To: "flynnnchen(陈天楚)" <flynnnchen@tencent.com>
Cc: krzk <krzk@kernel.org>, netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfc: port100: guard against incomplete USB frames
Date: Fri, 21 Nov 2025 19:45:09 +0000 [thread overview]
Message-ID: <aSDBRdt84f2O0Anp@horms.kernel.org> (raw)
In-Reply-To: <D9E78B690F07660A+202511171222138721171@tencent.com>
On Mon, Nov 17, 2025 at 12:22:15PM +0800, flynnnchen(陈天楚) wrote:
> Discovered by Atuin - Automated Vulnerability Discovery Engine.
>
> Validate that the URB payload is long enough for the frame header and the
> advertised data length before accessing it, so truncated transfers are
> rejected with -EIO, preventing the driver from reading out-of-bounds and
> leaking kernel memory to USB devices.
>
> Signed-off-by: Tianchu Chen <flynnnchen@tencent.com>
Thanks,
FWIIW, I agree with your analysis and solution.
I would add a fixes tag, as it is a fix for code present in the
net tree.
Perhaps this one: this seems to be the commit where the problem
was introduced.
Fixes: 0347a6ab300a ("NFC: port100: Commands mechanism implementation")
And it would be best to explicitly target such a fix at the net
tree, like this:
Subject: [PATCH net] ...
On a process note, as the from address of your email doesn't match
the Signed-off-by line, I think it would be best to include a From:
line at the very beginning of the commit message, with your name
matching the Signed-off-by line.
i.e.
From: Tianchu Chen <flynnnchen@tencent.com>
But over all this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2025-11-21 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 4:22 [PATCH] nfc: port100: guard against incomplete USB frames =?gb18030?B?Zmx5bm5uY2hlbiizwszss/4p?=
2025-11-21 19:45 ` Simon Horman [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=aSDBRdt84f2O0Anp@horms.kernel.org \
--to=horms@kernel.org \
--cc=flynnnchen@tencent.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.