From: Lukas Czerner <lczerner@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
bugzilla-daemon@kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [Bug 216283] New: FUZZ: BUG() triggered in fs/ext4/extent.c:ext4_ext_insert_extent() when mount and operate on crafted image
Date: Tue, 2 Aug 2022 11:28:37 +0200 [thread overview]
Message-ID: <20220802092837.wqgut2i6kkbehcof@fedora> (raw)
In-Reply-To: <20220801224551.GA3861211@dread.disaster.area>
On Tue, Aug 02, 2022 at 08:45:51AM +1000, Dave Chinner wrote:
--- snip ---
> >
> > Look, your entire argument hinges on the assumption that this is a
> > security vulnerability that could be exploited and the report makes the
> > situation worse. And that's very much debatable. I don't think it is and
> > Ted described it very well in his comment.
>
> On systems that automount filesytsems when you plug in a USB drive
> (which most distros do out of the box) then a crash bug during mount
> is, at minimum, an annoying DOS vector. And if it can result in a
> buffer overflow, then....
>
> > Asking for more information, or even asking reported to try to narrow
> > down the problem is of course fine.
>
> Sure, nobody is questioning how we triage these issues - the
> question is over how they are reported and the forum under which the
> initial triage takes place
>
> > But making sweeping claims about
> > moral and ethical responsibilities is always a little suspicious and
> > completely bogus in this case IMO.
>
> Hand waving away the fact that fuzzer crash bugs won't be a security
> issue without having done any investigation is pretty much the whole
> problem here. This is not responsible behaviour.
Since it's obvious that the security status of this is disputed, then
please feel free to create guidelines stating that fuzzer bugs for xfs
are considered a security issues and reporters should follow guidelines
of responsible disclosure and bugs are not to be reported publicly.
Problem solved and no moralizing needed.
-Lukas
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
next prev parent reply other threads:[~2022-08-02 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:35 [Bug 216283] New: FUZZ: BUG() triggered in fs/ext4/extent.c:ext4_ext_insert_extent() when mount and operate on crafted image bugzilla-daemon
2022-07-26 20:10 ` Darrick J. Wong
2022-07-27 11:53 ` Lukas Czerner
2022-07-27 23:22 ` Dave Chinner
2022-07-28 2:46 ` Theodore Ts'o
2022-08-02 3:25 ` Dave Chinner
2022-08-17 12:42 ` Zhang Boyang
2022-07-28 7:25 ` Lukas Czerner
2022-08-01 22:45 ` Dave Chinner
2022-08-02 1:06 ` Theodore Ts'o
2022-08-02 9:28 ` Lukas Czerner [this message]
2022-07-26 20:10 ` [Bug 216283] " bugzilla-daemon
2022-07-27 11:53 ` bugzilla-daemon
2022-07-27 23:22 ` bugzilla-daemon
2022-07-28 2:47 ` bugzilla-daemon
2022-07-28 7:25 ` bugzilla-daemon
2022-08-01 22:45 ` bugzilla-daemon
2022-08-02 1:06 ` bugzilla-daemon
2022-08-02 3:26 ` bugzilla-daemon
2022-08-02 9:28 ` bugzilla-daemon
2022-08-17 12:42 ` bugzilla-daemon
2022-10-04 9:15 ` bugzilla-daemon
2022-10-04 19:42 ` bugzilla-daemon
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=20220802092837.wqgut2i6kkbehcof@fedora \
--to=lczerner@redhat.com \
--cc=bugzilla-daemon@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.