From: Kees Cook <kees@kernel.org>
To: Duoming Zhou <duoming@zju.edu.cn>, linux-kernel@vger.kernel.org
Cc: brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev,
linux-wireless@vger.kernel.org, justinstitt@google.com,
jisoo.jang@yonsei.ac.kr, petr.tesarik.ext@huawei.com,
quic_alokad@quicinc.com, hdegoede@redhat.com,
keescook@chromium.org, johannes.berg@intel.com, kvalo@kernel.org,
arend.vanspriel@broadcom.com
Subject: Re: [PATCH v2] wifi: brcm80211: handle pmk_op allocation failure
Date: Wed, 28 Feb 2024 06:48:14 -0800 [thread overview]
Message-ID: <8B696743-9487-4A78-B9B4-16DA4F2F8E26@kernel.org> (raw)
In-Reply-To: <20240228063408.7006-1-duoming@zju.edu.cn>
On February 27, 2024 10:34:08 PM PST, 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")
>Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
>---
>Changes in v2:
> - Drop the new label and just return -ENOMEM.
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
>index 28d6a30cc01..7af6d6448b9 100644
>--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
>+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
>@@ -4322,6 +4322,9 @@ brcmf_pmksa_v3_op(struct brcmf_if *ifp, struct cfg80211_pmksa *pmksa,
> int ret;
>
> pmk_op = kzalloc(sizeof(*pmk_op), GFP_KERNEL);
>+ if (!pmk_op)
>+ ret = -ENOMEM;
This doesn't fix anything. It doesn't stop the execution path; it'll continue and immediately dereference the NULL pmk_op in the next line...
>+
> pmk_op->version = cpu_to_le16(BRCMF_PMKSA_VER_3);
>
> if (!pmksa) {
--
Kees Cook
next prev parent reply other threads:[~2024-02-28 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 6:34 Duoming Zhou
2024-02-28 12:54 ` Arend van Spriel
2024-02-28 14:48 ` Kees Cook [this message]
2024-02-28 15:46 ` Arend Van Spriel
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=8B696743-9487-4A78-B9B4-16DA4F2F8E26@kernel.org \
--to=kees@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=kvalo@kernel.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
all inboxes | Powered by JetHome®