Re: [BUG] ext4: NULL pointer dereference in jbd2_journal_file_inode() during inline data conversion
From: Theodore Tso
Date: Mon Nov 16 2026 - 16:40:12 EST
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