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>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025042436-iodize-dazzler-e7b2@gregkh>
Date: Thu, 24 Apr 2025 12:26:42 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Salvatore Bonaccorso <carnil@...ian.org>
Cc: Yu Kuai <yukuai1@...weicloud.com>, sashal@...nel.org,
	stable@...r.kernel.org, song@...nel.org, linux-raid@...r.kernel.org,
	linux-kernel@...r.kernel.org, yukuai3@...wei.com,
	yi.zhang@...wei.com, yangerkun@...wei.com, johnny.chenyi@...wei.com
Subject: Re: [PATCH 6.1 0/2] md: fix mddev uaf while iterating all_mddevs list

On Thu, Apr 24, 2025 at 11:32:52AM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
> 
> On Thu, Apr 24, 2025 at 08:40:41AM +0200, Greg KH wrote:
> > On Wed, Apr 23, 2025 at 08:14:09PM +0200, Salvatore Bonaccorso wrote:
> > > Hi Greg, Sasha, Yu,
> > > 
> > > On Sat, Apr 19, 2025 at 09:23:01AM +0800, Yu Kuai wrote:
> > > > From: Yu Kuai <yukuai3@...wei.com>
> > > > 
> > > > Hi, Greg
> > > > 
> > > > This is the manual adaptation version for 6.1, for 6.6/6.12 commit
> > > > 8542870237c3 ("md: fix mddev uaf while iterating all_mddevs list") can
> > > > be applied cleanly, can you queue them as well?
> > > > 
> > > > Thanks!
> > > > 
> > > > Yu Kuai (2):
> > > >   md: factor out a helper from mddev_put()
> > > >   md: fix mddev uaf while iterating all_mddevs list
> > > > 
> > > >  drivers/md/md.c | 50 +++++++++++++++++++++++++++++--------------------
> > > >  1 file changed, 30 insertions(+), 20 deletions(-)
> > > 
> > > I noticed that the change 8542870237c3 was queued for 6.6.y and 6.12.y
> > > and is in the review now, but wonder should we do something more with
> > > 6.1.y as this requires this series/manual adaption?
> > > 
> > > Or will it make for the next round of stable updates in 6.1.y? 
> > > 
> > > (or did it just felt through the cracks and it is actually fine that I
> > > ping the thread on this question).
> > 
> > This fell through the cracks and yes, it is great that you pinged it.
> > I'll queue it up for the next release, thanks!
> 
> Thank you! Very much appreciated! (People installing Debian will be
> happy as it affects kernel under certiain circumstances, cf.
> https://bugs.debian.org/1086175, https://bugs.debian.org/1089158, but
> was longstanding already).

Now queued up, thanks.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ