linux-cve-announce - CVE-2023-53570: wifi: nl80211: fix integer overflow in nl80211_parse_mbssid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100453-CVE-2023-53570-3733@gregkh>
Date: Sat,  4 Oct 2025 17:17:24 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53570: wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems()

nl80211_parse_mbssid_elems() uses a u8 variable num_elems to count the
number of MBSSID elements in the nested netlink attribute attrs, which can
lead to an integer overflow if a user of the nl80211 interface specifies
256 or more elements in the corresponding attribute in userspace. The
integer overflow can lead to a heap buffer overflow as num_elems determines
the size of the trailing array in elems, and this array is thereafter
written to for each element in attrs.

Note that this vulnerability only affects devices with the
wiphy->mbssid_max_interfaces member set for the wireless physical device
struct in the device driver, and can only be triggered by a process with
CAP_NET_ADMIN capabilities.

Fix this by checking for a maximum of 255 elements in attrs.

The Linux kernel CVE team has assigned CVE-2023-53570 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 5.16 with commit dc1e3cb8da8b414b37208b2fb6755fef8122504b and fixed in 6.1.46 with commit e642eb67b8c10dcce758d549cc81564116e0fa49
	Issue introduced in 5.16 with commit dc1e3cb8da8b414b37208b2fb6755fef8122504b and fixed in 6.4.11 with commit 7d09f9f255a5f78578deba5454923072bb53b16c
	Issue introduced in 5.16 with commit dc1e3cb8da8b414b37208b2fb6755fef8122504b and fixed in 6.5 with commit 6311071a056272e1e761de8d0305e87cc566f734

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-2023-53570
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/wireless/nl80211.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/e642eb67b8c10dcce758d549cc81564116e0fa49
	https://git.kernel.org/stable/c/7d09f9f255a5f78578deba5454923072bb53b16c
	https://git.kernel.org/stable/c/6311071a056272e1e761de8d0305e87cc566f734