From: Kalle Valo <kvalo@codeaurora.org>
To: Pkshih <pkshih@realtek.com>
Cc: Colin King <colin.king@canonical.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"kernel-janitors\@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] rtw89: Fix potential dereference of the null pointer sta
Date: Mon, 18 Oct 2021 15:11:45 +0300 [thread overview]
Message-ID: <87pms2ttvi.fsf@codeaurora.org> (raw)
In-Reply-To: <9cc681c217a449519aee524b35e6b6bc@realtek.com> (Pkshih's message of "Mon, 18 Oct 2021 03:35:28 +0000")
Pkshih <pkshih@realtek.com> writes:
>> -----Original Message-----
>> From: Colin King <colin.king@canonical.com>
>> Sent: Friday, October 15, 2021 11:46 PM
>> To: Kalle Valo <kvalo@codeaurora.org>; David S . Miller <davem@davemloft.net>; Jakub Kicinski
>> <kuba@kernel.org>; Pkshih <pkshih@realtek.com>; linux-wireless@vger.kernel.org;
>> netdev@vger.kernel.org
>> Cc: kernel-janitors@vger.kernel.org; linux-kernel@vger.kernel.org
>> Subject: [PATCH][next] rtw89: Fix potential dereference of the null pointer sta
>>
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> The pointer rtwsta is dereferencing pointer sta before sta is
>> being null checked, so there is a potential null pointer deference
>> issue that may occur. Fix this by only assigning rtwsta after sta
>> has been null checked. Add in a null pointer check on rtwsta before
>> dereferencing it too.
>>
>> Fixes: e3ec7017f6a2 ("rtw89: add Realtek 802.11ax driver")
>> Addresses-Coverity: ("Dereference before null check")
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/net/wireless/realtek/rtw89/core.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/wireless/realtek/rtw89/core.c
>> b/drivers/net/wireless/realtek/rtw89/core.c
>> index 06fb6e5b1b37..26f52a25f545 100644
>> --- a/drivers/net/wireless/realtek/rtw89/core.c
>> +++ b/drivers/net/wireless/realtek/rtw89/core.c
>> @@ -1534,9 +1534,14 @@ static bool rtw89_core_txq_agg_wait(struct rtw89_dev *rtwdev,
>> {
>> struct rtw89_txq *rtwtxq = (struct rtw89_txq *)txq->drv_priv;
>> struct ieee80211_sta *sta = txq->sta;
>> - struct rtw89_sta *rtwsta = (struct rtw89_sta *)sta->drv_priv;
>
> 'sta->drv_priv' is only a pointer, we don't really dereference the
> data right here, so I think this is safe. More, compiler can optimize
> this instruction that reorder it to the place just right before using.
> So, it seems like a false alarm.
>
>> + struct rtw89_sta *rtwsta;
>>
>> - if (!sta || rtwsta->max_agg_wait <= 0)
>> + if (!sta)
>> + return false;
>> + rtwsta = (struct rtw89_sta *)sta->drv_priv;
>> + if (!rtwsta)
>> + return false;
>> + if (rtwsta->max_agg_wait <= 0)
>> return false;
>>
>> if (rtwdev->stats.tx_tfc_lv <= RTW89_TFC_MID)
>
> I check the size of object files before/after this patch, and
> the original one is smaller.
>
> text data bss dec hex filename
> 16781 3392 1 20174 4ece core-0.o // original
> 16819 3392 1 20212 4ef4 core-1.o // after this patch
>
> Do you think it is worth to apply this patch?
I think that we should apply the patch. Even though the compiler _may_
reorder the code, it might choose not to do that.
Another question is that can txq->sta really be null? I didn't check the
code, but if it should be always set when the null check is not needed.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-10-18 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 15:45 [PATCH][next] rtw89: Fix potential dereference of the null pointer sta Colin King
2021-10-18 3:35 ` Pkshih
2021-10-18 12:11 ` Kalle Valo [this message]
2021-10-19 1:11 ` Pkshih
2021-10-20 8:36 ` Kalle Valo
2021-10-21 5:46 ` Pkshih
2021-10-21 8:48 ` Kalle Valo
2021-11-02 13:14 ` Dan Carpenter
2021-11-03 0:36 ` Pkshih
2021-11-03 10:21 ` Dan Carpenter
2021-11-04 1:38 ` Pkshih
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=87pms2ttvi.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.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 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.