From: "Theodore Ts'o" <tytso@mit.edu>
To: cheung wall <zzqq0103.hey@gmail.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: "WARNING in ext4_destroy_inode" in Linux Kernel v6.12-rc4
Date: Wed, 15 Jan 2025 00:00:15 -0500 [thread overview]
Message-ID: <20250115050015.GB1954680@mit.edu> (raw)
In-Reply-To: <CAKHoSAsxwS1J2fme+6-d84tguJGDYamVCHfcuXZbeGpTGHze0A@mail.gmail.com>
On Wed, Jan 15, 2025 at 10:34:24AM +0800, cheung wall wrote:
> Hello,
>
> I am writing to report a potential vulnerability identified in the
> Linux Kernel version v6.12-rc4. This vulnerability was discovered
> while i was testing the kernel.
A WARN_ON is not something I generally consider a "security
vulnerability". This is especially if (as I suspect) triggering
failure requires mounting a maliciously fuzzed file system image,
which is something I don't consider an interesting threat mode.
And without a reliable reproducer, I'm not likely to waste a lot of
time on this. So if you're a researcher trying to mess with Syzkaller
in some weird proprietary way without runninga proper syzbot
interface, sorry, this is a super-terrible way to try to demonstrate
real-world impact.
Feel free to do more of your own analysis, and when you have a
reliable reproucer, please let me know.
>
> Linux Kernel Repository Git Commit:
> 42f7652d3eb527d03665b09edac47f85fb600924 (tag: v6.12-rc4)
>
> Bug Location: 0010:ext4_destroy_inode+0x1d0/0x270 fs/ext4/super.c:1465
>
> Bug report: https://pastebin.com/YKFyLm5P
>
> Entire Log: https://pastebin.com/fE1tFAUS
For the record, this URL is not accessible; possibly because you
failed to make it be public.
> Thank you for your time and attention.
Sorry, but you've wasted my time.
- Ted
prev parent reply other threads:[~2025-01-15 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 2:34 cheung wall
2025-01-15 5:00 ` Theodore Ts'o [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=20250115050015.GB1954680@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zzqq0103.hey@gmail.com \
/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®