From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-27048: wifi: brcm80211: handle pmk_op allocation failure
Date: Wed, 1 May 2024 14:57:33 +0200 [thread overview]
Message-ID: <2024050114-CVE-2024-27048-016f@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: brcm80211: handle pmk_op allocation failure
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.
The Linux kernel CVE team has assigned CVE-2024-27048 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.4 with commit a96202acaea4 and fixed in 6.6.23 with commit df62e22c2e27
Issue introduced in 6.4 with commit a96202acaea4 and fixed in 6.7.11 with commit 9975908315c1
Issue introduced in 6.4 with commit a96202acaea4 and fixed in 6.8.2 with commit 6138a82f3bcc
Issue introduced in 6.4 with commit a96202acaea4 and fixed in 6.9-rc1 with commit b4152222e04c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-27048
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/df62e22c2e27420e8990a4f09e30d7bf56c2036f
https://git.kernel.org/stable/c/9975908315c13bae2f2ed5ba92870fa935180b0e
https://git.kernel.org/stable/c/6138a82f3bccfc67ed7ac059493579fc326c02e5
https://git.kernel.org/stable/c/b4152222e04cb8afeeca239c90e3fcaf4c553b42
reply other threads:[~2024-05-01 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2024050114-CVE-2024-27048-016f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).