[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024030255-CVE-2023-52530-ebf0@gregkh>
Date: Sat, 2 Mar 2024 22:53:14 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-52530: wifi: mac80211: fix potential key use-after-free
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: fix potential key use-after-free
When ieee80211_key_link() is called by ieee80211_gtk_rekey_add()
but returns 0 due to KRACK protection (identical key reinstall),
ieee80211_gtk_rekey_add() will still return a pointer into the
key, in a potential use-after-free. This normally doesn't happen
since it's only called by iwlwifi in case of WoWLAN rekey offload
which has its own KRACK protection, but still better to fix, do
that by returning an error code and converting that to success on
the cfg80211 boundary only, leaving the error for bad callers of
ieee80211_gtk_rekey_add().
The Linux kernel CVE team has assigned CVE-2023-52530 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.14 with commit fdf7cb4185b6 and fixed in 6.1.57 with commit 2f4e16e39e4f
Issue introduced in 4.14 with commit fdf7cb4185b6 and fixed in 6.5.7 with commit 65c72a720170
Issue introduced in 4.14 with commit fdf7cb4185b6 and fixed in 6.6 with commit 31db78a4923e
Please see https://www.kernel.org or 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-2023-52530
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:
net/mac80211/cfg.c
net/mac80211/key.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/2f4e16e39e4f5e78248dd9e51276a83203950b36
https://git.kernel.org/stable/c/65c72a7201704574dace708cbc96a8f367b1491d
https://git.kernel.org/stable/c/31db78a4923ef5e2008f2eed321811ca79e7f71b
Powered by blists - more mailing lists