Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wpa_supplicant: add upstream 2021-1 security fix
Date: Sun, 14 Mar 2021 21:32:46 +0100	[thread overview]
Message-ID: <87ft0x328h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210302215943.14131-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 2 Mar 2021 22:59:43 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issue:
 > - wpa_supplicant P2P provision discovery processing vulnerability (no CVE
 >   yet)

 > A vulnerability was discovered in how wpa_supplicant processes P2P
 > (Wi-Fi Direct) provision discovery requests. Under a corner case
 > condition, an invalid Provision Discovery Request frame could end up
 > reaching a state where the oldest peer entry needs to be removed. With
 > a suitably constructed invalid frame, this could result in use
 > (read+write) of freed memory. This can result in an attacker within
 > radio range of the device running P2P discovery being able to cause
 > unexpected behavior, including termination of the wpa_supplicant process
 > and potentially code execution.

 > For more details, see the advisory:
 > https://w1.fi/security/2021-1/wpa_supplicant-p2p-provision-discovery-processing-vulnerability.txt

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2020.02.x and 2020.11.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2021-03-14 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 21:59 [Buildroot] [PATCH] package/wpa_supplicant: add upstream 2021-1 security fix Peter Korsgaard
2021-03-02 22:12 ` Yann E. MORIN
2021-03-14 20:32 ` Peter Korsgaard [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=87ft0x328h.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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