[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021859-CVE-2025-71227-949c@gregkh>
Date: Wed, 18 Feb 2026 15:22:02 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71227: wifi: mac80211: don't WARN for connections on invalid channels
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: don't WARN for connections on invalid channels
It's not clear (to me) how exactly syzbot managed to hit this,
but it seems conceivable that e.g. regulatory changed and has
disabled a channel between scanning (channel is checked to be
usable by cfg80211_get_ies_channel_number) and connecting on
the channel later.
With one scenario that isn't covered elsewhere described above,
the warning isn't good, replace it with a (more informative)
error message.
The Linux kernel CVE team has assigned CVE-2025-71227 to this issue.
Affected and fixed versions
===========================
Fixed in 6.18.10 with commit 10d3ff7e5812c8d70300f6fa8f524009a06aa7e1
Fixed in 6.19 with commit 99067b58a408a384d2a45c105eb3dce980a862ce
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-2025-71227
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/mlme.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/10d3ff7e5812c8d70300f6fa8f524009a06aa7e1
https://git.kernel.org/stable/c/99067b58a408a384d2a45c105eb3dce980a862ce
Powered by blists - more mailing lists