From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "cve@kernel.org" <cve@kernel.org>,
"linux-cve-announce@vger.kernel.org"
<linux-cve-announce@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2024-27410: wifi: nl80211: reject iftype change with mesh ID change
Date: Wed, 22 May 2024 12:28:59 +0000 [thread overview]
Message-ID: <42c2fa68c360d05dcf798bc783078270e8fe8314.camel@oracle.com> (raw)
In-Reply-To: <2024051701-CVE-2024-27410-874a@gregkh>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Fri, 17 May 2024 13:52:02 +0200, Greg Kroah-Hartman wrote:
> In the Linux kernel, the following vulnerability has been resolved:
>
> wifi: nl80211: reject iftype change with mesh ID change
>
> It's currently possible to change the mesh ID when the
> interface isn't yet in mesh mode, at the same time as
> changing it into mesh mode. This leads to an overwrite
> of data in the wdev->u union for the interface type it
> currently has, causing cfg80211_change_iface() to do
> wrong things when switching.
>
> [...]
>
> The Linux kernel CVE team has assigned CVE-2024-27410 to this issue.
This does not apply to versions below 6.0, as the union was not backported.
The fix commit mentioned is incorrect, it should be 7b0a0e3c3a88.
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2024-05-22 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024051701-CVE-2024-27410-874a@gregkh>
2024-05-22 12:28 ` Siddh Raman Pant [this message]
2024-05-22 12:34 ` CVE-2024-27410: wifi: nl80211: reject iftype change with mesh ID change gregkh
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=42c2fa68c360d05dcf798bc783078270e8fe8314.camel@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox