mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Christian Brauner <brauner@kernel.org>,
	David Sterba <dsterba@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
	now4yreal <now4yreal@foxmail.com>, Jan Kara <jack@suse.com>,
	Viro <viro@zeniv.linux.org.uk>, Bacik <josef@toxicpanda.com>,
	Stone <leocstone@gmail.com>, Sandeen <sandeen@redhat.com>,
	Johnson <jeff.johnson@oss.qualcomm.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug Report] OOB-read BUG in HFS+ filesystem
Date: Tue, 15 Apr 2025 09:16:58 +0000	[thread overview]
Message-ID: <786f0a0e-8cea-4007-bbae-2225fcca95b4@wdc.com> (raw)
In-Reply-To: <20250415-wohin-anfragen-90b2df73295b@brauner>

On 15.04.25 09:52, Christian Brauner wrote:
> On Mon, Apr 14, 2025 at 06:23:28PM +0200, David Sterba wrote:
>> On Mon, Apr 14, 2025 at 03:21:56PM +0100, Matthew Wilcox wrote:
>>> On Mon, Apr 14, 2025 at 04:18:27PM +0200, Christian Brauner wrote:
>>>> On Mon, Apr 14, 2025 at 09:45:25PM +0800, now4yreal wrote:
>>>>> Dear Linux Security Maintainers,
>>>>> I would like to report a OOB-read vulnerability in the HFS+ file
>>>>> system, which I discovered using our in-house developed kernel fuzzer,
>>>>> Symsyz.
>>>>
>>>> Bug reports from non-official syzbot instances are generally not
>>>> accepted.
>>>>
>>>> hfs and hfsplus are orphaned filesystems since at least 2014. Bug
>>>> reports for such filesystems won't receive much attention from the core
>>>> maintainers.
>>>>
>>>> I'm very very close to putting them on the chopping block as they're
>>>> slowly turning into pointless burdens.
>>>
>>> I've tried asking some people who are long term Apple & Linux people,
>>> but haven't been able to find anyone interested in becoming maintainer.
>>> Let's drop both hfs & hfsplus.  Ten years of being unmaintained is
>>> long enough.
>>
>> Agreed. If needed there are FUSE implementations to access .dmg files
>> with HFS/HFS+ or other standalone tools.
>>
>> https://github.com/0x09/hfsfuse
>> https://github.com/darlinghq/darling-dmg
> 
> Ok, I'm open to trying. I'm adding a deprecation message when initating
> a new hfs{plus} context logged to dmesg and then we can try and remove
> it by the end of the year.
> 
> 

Just a word of caution though, (at least Intel) Macs have their EFI ESP 
partition on HFS+ instead of FAT. I don't own an Apple Silicon Mac so I 
can't check if it's there as well.

  reply	other threads:[~2025-04-15  9:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 13:45 =?gb18030?B?bm93NHlyZWFs?=
2025-04-14 14:18 ` Christian Brauner
2025-04-14 14:21   ` Matthew Wilcox
2025-04-14 16:23     ` David Sterba
2025-04-15  7:52       ` Christian Brauner
2025-04-15  9:16         ` Johannes Thumshirn [this message]
2025-04-15  9:31           ` Christian Brauner
2025-04-15 10:23             ` Johannes Thumshirn
2025-04-15 11:25               ` Christian Brauner

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=786f0a0e-8cea-4007-bbae-2225fcca95b4@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=brauner@kernel.org \
    --cc=dsterba@suse.cz \
    --cc=jack@suse.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=josef@toxicpanda.com \
    --cc=leocstone@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=now4yreal@foxmail.com \
    --cc=sandeen@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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®