The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Ahmed Khan <ahmadpsn95@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ext4: NULL pointer dereference in jbd2_journal_file_inode() during inline data conversion
Date: Mon, 16 Nov 2026 16:39:53 -0500	[thread overview]
Message-ID: <avt1ObnHmA4AmSmc@mit.edu> (raw)
In-Reply-To: <CAOaS1==g3mdoqmS2AjOC0_-woXJbA_X0LJQt7+M7d1=+gfyQqw@mail.gmail.com>

On Sat, Nov 14, 2026 at 07:43:08PM -0500, Ahmed Khan wrote:
> 
> My name is Ahmed Khan, I am a security researcher from Canada. I
> believe I found a bug within the Linux Kernel, specifically, version
> 7.3.4 affecting all major distros. I will be candid and state that I
> used AI heavily in fuzzing the kernel using "syzkaller"....

When you say "syzkaller", are you referring to your own instance of
syzkaller, which you may have modified to use AI-directed fuzzing?

> This corresponds to syzbot crash ID:
> 3eb9083d961b1b97587d103692546ba06797de4e

This crash ID doesn't appear to be one which is recognized by
https://syzkaller.appspot.com --- which would make sense if it's your
own Syzkaller instance.

> Please let me know if you would like the standalone C reproducer or
> the minimal ext4 disk image attached inline. I have this in a private
> repo and would be happy to add you as a project contributor.

Yes, please send the standalone C reproducer and minimal crafted ext4 image.
That would be most helpful.

Note that we don't really consider crashes which require a crafted
file system image to trigger to be a security vulnerability, unless
the file system corruption is not caught by e2fsck (or triggers a
memory pointer bug or other issue in e2fsck).  Not running fsck on an
untrusted file system before introducing it to the Trusted Computing
Base of the linux kernel is roughly equivalent to running "dd
if=/dev/zero of=/dev/mem".  Sure, it might crash the system, but
that's really a PEBCAK system administrator issue.  :-)

Regards,

					- Ted

      reply	other threads:[~2026-11-16 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  0:43 [BUG] ext4: NULL pointer dereference in jbd2_journal_file_inode() during inline data conversion Ahmed Khan
2026-11-16 21:39 ` Theodore Tso [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=avt1ObnHmA4AmSmc@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=ahmadpsn95@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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