syzkaller-bugs

1–30 of 8810

Linux kernel bugs found with syzkaller fuzzer and reported automatically by syzbot.

Nobody is reading this list per se. See this article on reporting kernel bugs.

0 selected

syzbot, s...@google.com9

3:31 PM

[syzbot] KASAN: slab-out-of-bounds Write in copy_verifier_state

syzbot suspects this issue was fixed by commit: commit 45435d8da71f9f3e6860e6e6ea9667b6ec17ec64

unread,

[syzbot] KASAN: slab-out-of-bounds Write in copy_verifier_state

syzbot suspects this issue was fixed by commit: commit 45435d8da71f9f3e6860e6e6ea9667b6ec17ec64

3:31 PM

syzbot, Hillf Danton3

12:15 PM

[syzbot] kernel BUG in process_one_work

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel

unread,

[syzbot] kernel BUG in process_one_work

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel

12:15 PM

syzbot, … Luis Chamberlain11

10:54 AM

[syzbot] WARNING: locking bug in umh_complete

On Sat, Feb 04, 2023 at 09:48:39AM +0900, Tetsuo Handa wrote: > On 2023/02/03 23:31, Peter

unread,

[syzbot] WARNING: locking bug in umh_complete

On Sat, Feb 04, 2023 at 09:48:39AM +0900, Tetsuo Handa wrote: > On 2023/02/03 23:31, Peter

10:54 AM

7:05 AM

[syzbot] KMSAN: uninit-value in hfs_brec_find

syzbot has found a reproducer for the following issue on: HEAD commit: eda666ff2276 kmsan: silence -

unread,

[syzbot] KMSAN: uninit-value in hfs_brec_find

syzbot has found a reproducer for the following issue on: HEAD commit: eda666ff2276 kmsan: silence -

7:05 AM

syzbot, Aleksandr Nogikh4

5:21 AM

[syzbot] BUG: unable to handle kernel NULL pointer dereference in ni_find_attr

On Sun, Feb 5, 2023 at 8:46 PM syzbot <syzbot+69d15c...@syzkaller.appspotmail.com>

unread,

[syzbot] BUG: unable to handle kernel NULL pointer dereference in ni_find_attr

On Sun, Feb 5, 2023 at 8:46 PM syzbot <syzbot+69d15c...@syzkaller.appspotmail.com>

5:21 AM

syzbot, … patchwork-b...@kernel.org7

5:14 AM

[syzbot] WARNING in __usbnet_read_cmd/usb_submit_urb

Hello: This patch was applied to netdev/net.git (master) by David S. Miller <da...@davemloft.net

unread,

[syzbot] WARNING in __usbnet_read_cmd/usb_submit_urb

Hello: This patch was applied to netdev/net.git (master) by David S. Miller <da...@davemloft.net

5:14 AM

syzbot, Aleksandr Nogikh4

5:10 AM

[syzbot] BUG: unable to handle kernel paging request in mi_enum_attr

On Sat, Feb 4, 2023 at 2:56 PM syzbot <syzbot+28207a...@syzkaller.appspotmail.com>

unread,

[syzbot] BUG: unable to handle kernel paging request in mi_enum_attr

On Sat, Feb 4, 2023 at 2:56 PM syzbot <syzbot+28207a...@syzkaller.appspotmail.com>

5:10 AM

4:57 AM

[syzbot] WARNING in l2cap_do_send

Hello, syzbot found the following issue on: HEAD commit: 64466c407a73 Merge git://git.kernel.org/pub/

unread,

[syzbot] WARNING in l2cap_do_send

Hello, syzbot found the following issue on: HEAD commit: 64466c407a73 Merge git://git.kernel.org/pub/

4:57 AM

3:58 AM

[syzbot] BUG: unable to handle kernel paging request in vfs_rename

Hello, syzbot found the following issue on: HEAD commit: d2d11f342b17 Merge branch 'fixes' of

unread,

[syzbot] BUG: unable to handle kernel paging request in vfs_rename

Hello, syzbot found the following issue on: HEAD commit: d2d11f342b17 Merge branch 'fixes' of

3:58 AM

syzbot, Hillf Danton6

Feb 5

[syzbot] general protection fault in __blk_rq_map_sg

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: general

unread,

[syzbot] general protection fault in __blk_rq_map_sg

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: general

Feb 5

syzbot, Hillf Danton7

Feb 5

[syzbot] kernel BUG in __tlb_remove_page_size (2)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

unread,

[syzbot] kernel BUG in __tlb_remove_page_size (2)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

Feb 5

syzbot, Hillf Danton7

Feb 5

[syzbot] WARNING in kernfs_get (4)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

unread,

[syzbot] WARNING in kernfs_get (4)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

Feb 5

syzbot, ead...@sina.com5

Feb 5

[syzbot] [f2fs?] KASAN: use-after-free Write in __attach_extent_node

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: KASAN:

unread,

[syzbot] [f2fs?] KASAN: use-after-free Write in __attach_extent_node

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: KASAN:

Feb 5

syzbot, ead...@sina.com3

Feb 4

[syzbot] [f2fs?] KASAN: use-after-free Read in __shrink_extent_tree

> From: Edward Adam Davis <ead...@sina.com> > > On Date: Tue, 31 Jan 2023 05:48:49 -

unread,

[syzbot] [f2fs?] KASAN: use-after-free Read in __shrink_extent_tree

> From: Edward Adam Davis <ead...@sina.com> > > On Date: Tue, 31 Jan 2023 05:48:49 -

Feb 4

Feb 4

[syzbot] BUG: unable to handle kernel paging request in writeback_single_inode (2)

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] BUG: unable to handle kernel paging request in writeback_single_inode (2)

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 4

syzbot, … ead...@sina.com43

Feb 4

[syzbot] [gfs2?] KASAN: use-after-free Read in qd_unlock (2)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

unread,

[syzbot] [gfs2?] KASAN: use-after-free Read in qd_unlock (2)

Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO:

Feb 4

syzbot, … Taehee Yoo11

Feb 4

[syzbot] kernel panic: kernel stack overflow

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] kernel panic: kernel stack overflow

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 4

Feb 4

[syzbot] BUG: looking up invalid subclass: ADDR

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] BUG: looking up invalid subclass: ADDR

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 4

Feb 4

[syzbot] general protection fault in ntfs_set_inode

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] general protection fault in ntfs_set_inode

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 4

syzbot, … Bart Van Assche5

Feb 3

[syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode

On 2/3/23 00:53, syzbot wrote: > syzbot has bisected this issue to: > > commit

unread,

[syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode

On 2/3/23 00:53, syzbot wrote: > syzbot has bisected this issue to: > > commit

Feb 3

syzbot, … Dmitry Vyukov6

Feb 3

[syzbot] stack segment fault in truncate_inode_pages_final

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] stack segment fault in truncate_inode_pages_final

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 3

syzbot, … Christoph Hellwig3

Feb 3

[syzbot] [ntfs3?] [btrfs?] BUG: unable to handle kernel paging request in clear_user_rep_good

Where are the ntfs3 and btrfs tags coming from? This seems to clearly be about ext4 in the call stack

unread,

[syzbot] [ntfs3?] [btrfs?] BUG: unable to handle kernel paging request in clear_user_rep_good

Where are the ntfs3 and btrfs tags coming from? This seems to clearly be about ext4 in the call stack

Feb 3

syzbot, … Christoph Hellwig16

Feb 3

[syzbot] general protection fault in skb_dequeue (3)

On Fri, Feb 03, 2023 at 04:27:10PM +0000, David Howells wrote: > Hi Christoph, > > What does

unread,

[syzbot] general protection fault in skb_dequeue (3)

On Fri, Feb 03, 2023 at 04:27:10PM +0000, David Howells wrote: > Hi Christoph, > > What does

Feb 3

Feb 3

[syzbot] general protection fault in __nilfs_btree_get_block

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

unread,

[syzbot] general protection fault in __nilfs_btree_get_block

Auto-closing this bug as obsolete. Crashes did not happen for a while, no reproducer and no activity.

Feb 3

Feb 3

[syzbot] WARNING: locking bug in nci_close_device

Hello, syzbot found the following issue on: HEAD commit: 6d796c50f84c Linux 6.2-rc6 git tree:

unread,

[syzbot] WARNING: locking bug in nci_close_device

Hello, syzbot found the following issue on: HEAD commit: 6d796c50f84c Linux 6.2-rc6 git tree:

Feb 3

Feb 3

[syzbot] possible deadlock in skb_queue_tail (5)

Hello, syzbot found the following issue on: HEAD commit: 9f266ccaa2f5 Merge tag 'for_linus'

unread,

[syzbot] possible deadlock in skb_queue_tail (5)

Hello, syzbot found the following issue on: HEAD commit: 9f266ccaa2f5 Merge tag 'for_linus'

Feb 3

syzbot, Tetsuo Handa2

Feb 3

[syzbot] WARNING: locking bug in process_one_work (4)

#syz dup: WARNING: locking bug in umh_complete

unread,

[syzbot] WARNING: locking bug in process_one_work (4)

#syz dup: WARNING: locking bug in umh_complete

Feb 3

Feb 3

[syzbot] WARNING in remove_proc_entry (5)

Hello, syzbot found the following issue on: HEAD commit: 80bd9028feca Add linux-next specific files

unread,

[syzbot] WARNING in remove_proc_entry (5)

Hello, syzbot found the following issue on: HEAD commit: 80bd9028feca Add linux-next specific files

Feb 3

syzbot, … Dmitry Vyukov5

Feb 3

[syzbot] WARNING in check_map_prog_compatibility

On Fri, 3 Feb 2023 at 00:06, syzbot <syzbot+e3f8d4...@syzkaller.appspotmail.com>

unread,

[syzbot] WARNING in check_map_prog_compatibility

On Fri, 3 Feb 2023 at 00:06, syzbot <syzbot+e3f8d4...@syzkaller.appspotmail.com>

Feb 3

Feb 2

[syzbot] BUG: unable to handle kernel NULL pointer dereference in klist_next

Auto-closing this bug as obsolete. No recent activity, existing reproducers are no longer triggering

unread,

[syzbot] BUG: unable to handle kernel NULL pointer dereference in klist_next

Auto-closing this bug as obsolete. No recent activity, existing reproducers are no longer triggering

Feb 2

Search

Clear search

Close search

Google apps

Main menu