mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: David Sterba <dsterba@suse.cz>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2025-40128: btrfs: fix symbolic link reading when bs > ps
Date: Thu, 13 Nov 2025 12:37:53 -0500	[thread overview]
Message-ID: <2025111342-maroon-untouched-02a8@gregkh> (raw)
In-Reply-To: <20251113104008.GM13846@twin.jikos.cz>

On Thu, Nov 13, 2025 at 11:40:08AM +0100, David Sterba wrote:
> On Wed, Nov 12, 2025 at 07:24:04PM +0900, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> > 
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > btrfs: fix symbolic link reading when bs > ps
> > 
> > [BUG DURING BS > PS TEST]
> > When running the following script on a btrfs whose block size is larger
> > than page size, e.g. 8K block size and 4K page size, it will trigger a
> > kernel BUG:
> > 
> >   # mkfs.btrfs -s 8k $dev
> >   # mount $dev $mnt
> >   # mkdir $mnt/dir
> >   # ln -s dir $mnt/link
> >   # ls $mnt/link
> 
> Please drop the CVE status from this patch, the bs > ps (block size
> bigger than page size) feature requires CONFIG_BTRFS_EXPERIMENTAL and is
> unfinished and possibly unstable in other use cases. It does not make
> sense to improve security where none should be expected.

Oops, good catch, now rejected, thanks for the review!

greg k-h

      reply	other threads:[~2025-11-13 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025111253-CVE-2025-40128-2dd9@gregkh>
2025-11-13 10:40 ` David Sterba
2025-11-13 17:37   ` Greg Kroah-Hartman [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=2025111342-maroon-untouched-02a8@gregkh \
    --to=gregkh@kernel.org \
    --cc=cve@kernel.org \
    --cc=dsterba@suse.cz \
    --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

all inboxes | Powered by JetHome®