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
On Wed, May 22, 2024 at 12:28:59PM +0000, Siddh Raman Pant wrote:
> 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.
Changelogs should be written a bit more careful then :)
Note, that commit was backported to 5.19.2, so 6.0 is not correct...
I'll go update the cve and push out a json update to cve.org with this
information, thanks for letting us know!
Also, this commit was backported to the older kernels, so this is going
to look strange, here's the new text:
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 4.19.309 with commit d38d31bbbb9d
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 5.4.271 with commit 0cfbb26ee5e7
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 5.10.212 with commit 99eb2159680a
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 5.15.151 with commit 063715c33b4c
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 6.1.81 with commit 930e826962d9
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 6.6.21 with commit 177d574be4b5
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 6.7.9 with commit a2add961a5ed
+ Issue introduced in 6.0 with commit 7b0a0e3c3a88 and fixed in 6.8 with commit f78c1375339a
Hopefully people's json parsers can handle that well :)
thanks,
greg k-h