Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Stefan Nürnberger" <stefan.nuernberger@cyberus-technology.de>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"lwn@lwn.net" <lwn@lwn.net>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"jslaby@suse.cz" <jslaby@suse.cz>
Subject: Re: Linux 6.13.3
Date: Mon, 17 Feb 2025 14:25:16 +0100	[thread overview]
Message-ID: <2025021704-region-calzone-7d24@gregkh> (raw)
In-Reply-To: <a082db2605514513a0a8568382d5bd2b6f1877a0.camel@cyberus-technology.de>

On Mon, Feb 17, 2025 at 12:41:58PM +0000, Stefan Nürnberger wrote:
> Please revert the commit titled
> "vfio/platform: check the bounds of read/write syscalls" from all the
> latest stable releases (6.13.3, 6.12.14, 6.6.78).

Ah, the joys of patch :(

> The backport was already included in the releases two weeks ago and the
> new one doubles up the existing check. The full list of fixed versions
> (back to 5.4) is correctly mentioned in the associated CVE:
> https://www.cve.org/CVERecord/?id=CVE-2025-21687

And that CVE record now shows the duplicates as well, remember, we keep
them up to date when new stable kernels are released.

I'll go revert this for the next round of kernels, but it's not really a
problem with checking the same thing twice, so nothing is broken.

thanks,

greg k-h

      reply	other threads:[~2025-02-17 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 10:39 Linux 6.13.3 Greg Kroah-Hartman
2025-02-17 10:39 ` Greg Kroah-Hartman
2025-02-17 12:41 ` Stefan Nürnberger
2025-02-17 13:25   ` gregkh [this message]

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=2025021704-region-calzone-7d24@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=stefan.nuernberger@cyberus-technology.de \
    --cc=torvalds@linux-foundation.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