From: Kalle Valo <kvalo@kernel.org>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev,
linux-wireless@vger.kernel.org, justinstitt@google.com,
quic_alokad@quicinc.com, jisoo.jang@yonsei.ac.kr,
petr.tesarik.ext@huawei.com, hdegoede@redhat.com,
keescook@chromium.org, johannes.berg@intel.com,
arend.vanspriel@broadcom.com, Duoming Zhou <duoming@zju.edu.cn>
Subject: Re: [PATCH v3] wifi: brcm80211: handle pmk_op allocation failure
Date: Tue, 5 Mar 2024 18:56:21 +0000 (UTC) [thread overview]
Message-ID: <170966497987.424347.4050351610859400431.kvalo@kernel.org> (raw)
In-Reply-To: <20240229103153.18533-1-duoming@zju.edu.cn>
Duoming Zhou <duoming@zju.edu.cn> wrote:
> The kzalloc() in brcmf_pmksa_v3_op() will return null if the
> physical memory has run out. As a result, if we dereference
> the null value, the null pointer dereference bug will happen.
>
> Return -ENOMEM from brcmf_pmksa_v3_op() if kzalloc() fails
> for pmk_op.
>
> Fixes: a96202acaea4 ("wifi: brcmfmac: cfg80211: Add support for PMKID_V3 operations")
> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> Reviewed-by: Kees Cook <keescook@chromium.org>
Patch applied to wireless-next.git, thanks.
b4152222e04c wifi: brcm80211: handle pmk_op allocation failure
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240229103153.18533-1-duoming@zju.edu.cn/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-03-05 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 10:31 [PATCH v3] wifi: brcm80211: handle pmk_op allocation failure Duoming Zhou
2024-02-29 11:36 ` Arend van Spriel
2024-03-01 0:40 ` Kees Cook
2024-03-05 18:56 ` Kalle Valo [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=170966497987.424347.4050351610859400431.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=duoming@zju.edu.cn \
--cc=hdegoede@redhat.com \
--cc=jisoo.jang@yonsei.ac.kr \
--cc=johannes.berg@intel.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=petr.tesarik.ext@huawei.com \
--cc=quic_alokad@quicinc.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