From: Krzysztof Kozlowski <krzk@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>,
Aleksandr Mishin <amishin@t-argos.ru>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH v2] nfc: pn533: Add poll mod list filling check
Date: Thu, 29 Aug 2024 11:06:34 +0200 [thread overview]
Message-ID: <b1088e86-a88e-4e20-9923-940dfba5dea8@kernel.org> (raw)
In-Reply-To: <26d3f7cf-1fd8-48b6-97be-ba6819a2ff85@redhat.com>
On 29/08/2024 10:26, Paolo Abeni wrote:
>
>
> On 8/27/24 10:48, Aleksandr Mishin wrote:
>> In case of im_protocols value is 1 and tm_protocols value is 0 this
>> combination successfully passes the check
>> 'if (!im_protocols && !tm_protocols)' in the nfc_start_poll().
>> But then after pn533_poll_create_mod_list() call in pn533_start_poll()
>> poll mod list will remain empty and dev->poll_mod_count will remain 0
>> which lead to division by zero.
>>
>> Normally no im protocol has value 1 in the mask, so this combination is
>> not expected by driver. But these protocol values actually come from
>> userspace via Netlink interface (NFC_CMD_START_POLL operation). So a
>> broken or malicious program may pass a message containing a "bad"
>> combination of protocol parameter values so that dev->poll_mod_count
>> is not incremented inside pn533_poll_create_mod_list(), thus leading
>> to division by zero.
>> Call trace looks like:
>> nfc_genl_start_poll()
>> nfc_start_poll()
>> ->start_poll()
>> pn533_start_poll()
>>
>> Add poll mod list filling check.
>>
>> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>>
>> Fixes: dfccd0f58044 ("NFC: pn533: Add some polling entropy")
>> Signed-off-by: Aleksandr Mishin <amishin@t-argos.ru>
>
> The issue looks real to me and the proposed fix the correct one, but
> waiting a little more for Krzysztof feedback, as he expressed concerns
> on v1.
There was one month delay between my reply and clarifications from
Fedor, so original patch is neither in my mailbox nor in my brain.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
However different problem is: shouldn't as well or instead
nfc_genl_start_poll() validate the attributes received by netlink?
We just pass them directly to the drivers and several other drivers
might not expect random stuff there.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-29 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 9:39 [PATCH] " Aleksandr Mishin
2024-07-03 5:02 ` Krzysztof Kozlowski
2024-07-03 7:26 ` Aleksandr Mishin
2024-07-04 12:07 ` Krzysztof Kozlowski
2024-08-05 8:47 ` [lvc-project] " Fedor Pchelkin
2024-08-27 8:48 ` [PATCH v2] " Aleksandr Mishin
2024-08-29 8:26 ` Paolo Abeni
2024-08-29 8:30 ` Paolo Abeni
2024-08-29 9:06 ` Krzysztof Kozlowski [this message]
2024-08-29 9:33 ` Paolo Abeni
2024-08-29 9:34 ` Paolo Abeni
2024-08-29 10:02 ` Krzysztof Kozlowski
2024-08-29 10:21 ` 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=b1088e86-a88e-4e20-9923-940dfba5dea8@kernel.org \
--to=krzk@kernel.org \
--cc=amishin@t-argos.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®