archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <>
To: Eric Biggers <>
Cc: Sergej Schumilo <>,,,,,
	Linus Torvalds <>,
	Cornelius Aschermann <>
Subject: Re: Null-Pointer Deference in hfs.ko (Linux 4.15.0-15.16 Ubuntu)
Date: Wed, 18 Apr 2018 19:43:58 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Apr 18, 2018 at 10:54:21AM -0700, Eric Biggers wrote:
> Also Sergej, I know that you want to consider this a "security bug" and report
> it to "security" teams, and maybe even file a CVE number.  But the reality is
> that NULL pointer dereferences rarely have much security impact, and many
> "security" teams seem to be wasting so much time with such bugs that they are
> ignoring bugs with actual security impact, like the 34 use-after-free bugs that
> are currently open in the syzbot dashbard.  So IMO, going through the full
> security circus on NULL pointer dereferences is actually detriminal to security.
> (Though, they still need to be fixed of course!)

I don't think this really needs to be fixed.  I think the security bug
is that Ubuntu have configured their system in such a way that it will
attempt to automount an HFS filesystem on a USB key.  By going through
FUSE or some other userspace filesystem, the security risk would be

Is it time to start moving unmaintained obsolescent filesystems with
few remaining users into staging?  ... Hey, that sounds like a good
topic for next week!

  reply	other threads:[~2018-04-19  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 16:26 Null-Pointer Deference in hfs.ko (Linux 4.15.0-15.16 Ubuntu) Sergej Schumilo
2018-04-18 17:30 ` Matthew Wilcox
2018-04-18 17:54   ` Eric Biggers
2018-04-19  2:43     ` Matthew Wilcox [this message]
2018-04-18 17:59   ` Darrick J. Wong
2018-04-19  1:44     ` Dave Chinner
2018-04-19  2:15       ` Darrick J. Wong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).