From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53113: wifi: nl80211: fix NULL-ptr deref in offchan check
Date: Fri, 2 May 2025 17:56:18 +0200 [thread overview]
Message-ID: <2025050228-CVE-2023-53113-a3ff@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: nl80211: fix NULL-ptr deref in offchan check
If, e.g. in AP mode, the link was already created by userspace
but not activated yet, it has a chandef but the chandef isn't
valid and has no channel. Check for this and ignore this link.
The Linux kernel CVE team has assigned CVE-2023-53113 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1 and fixed in 6.1.21 with commit 87e80ea4fbc9ce2f2005905fdbcd38baaa47463a
Issue introduced in 6.0 with commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1 and fixed in 6.2.8 with commit 201a836c2385fdd2b9d0a8e7737bba5b26f1863a
Issue introduced in 6.0 with commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1 and fixed in 6.3 with commit f624bb6fad23df3270580b4fcef415c6e7bf7705
Issue introduced in 5.19.2 with commit 7a53ad13c09150076b7ddde96c2dfc5622c90b45
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-53113
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/87e80ea4fbc9ce2f2005905fdbcd38baaa47463a
https://git.kernel.org/stable/c/201a836c2385fdd2b9d0a8e7737bba5b26f1863a
https://git.kernel.org/stable/c/f624bb6fad23df3270580b4fcef415c6e7bf7705
reply other threads:[~2025-05-02 16:01 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=2025050228-CVE-2023-53113-a3ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.