From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Thalmeier <michael.thalmeier@hale.at>,
Deepak Sharma <deepak.sharma.472935@gmail.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Simon Horman <horms@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"Lukas K ." <kernel@0x83.eu>,
Michael Thalmeier <michael@thalmeier.at>,
stable@vger.kernel.org
Subject: Re: [PATCH net v6] net: nfc: nci: Fix parameter validation for packet data
Date: Wed, 18 Feb 2026 09:50:55 +0100 [thread overview]
Message-ID: <7c66f175-3637-478f-9d0e-e314bff59ddf@kernel.org> (raw)
In-Reply-To: <20260218083000.301354-1-michael.thalmeier@hale.at>
On 18/02/2026 09:30, Michael Thalmeier wrote:
> Since commit 9c328f54741b ("net: nfc: nci: Add parameter validation for
> packet data") communication with nci nfc chips is not working any more.
>
> The mentioned commit tries to fix access of uninitialized data, but
> failed to understand that in some cases the data packet is of variable
> length and can therefore not be compared to the maximum packet length
> given by the sizeof(struct).
>
> Fixes: 9c328f54741b ("net: nfc: nci: Add parameter validation for packet data")
> Cc: stable@vger.kernel.org
> Signed-off-by: Michael Thalmeier <michael.thalmeier@hale.at>
I am trying to get it retested by syzbot for the original issue, to be
sure the original report is still fixed.
I sent:
Reported-by: syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=740e04c2a93467a0f8c8
#syz unfix
And then followed by Reported+Closes+:
#syz test
but syzbot does not want to retest it:
"This bug is already marked as fixed. No point in testing."
Anyone knows how to re-test this against old report?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-18 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 8:30 [PATCH net v6] net: nfc: nci: Fix parameter validation for packet data Michael Thalmeier
2026-02-18 8:50 ` Krzysztof Kozlowski [this message]
2026-02-19 17:40 ` 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=7c66f175-3637-478f-9d0e-e314bff59ddf@kernel.org \
--to=krzk@kernel.org \
--cc=deepak.sharma.472935@gmail.com \
--cc=horms@kernel.org \
--cc=kernel@0x83.eu \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thalmeier@hale.at \
--cc=michael@thalmeier.at \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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.