syzkaller-bugs

Contact owners and managers

1–30 of 14621

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

6:05 PM

[syzbot] [fbdev?] BUG: unable to handle kernel paging request in bitfill_aligned (4)

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

unread,

[syzbot] [fbdev?] BUG: unable to handle kernel paging request in bitfill_aligned (4)

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

6:05 PM

syzbot, Christian Brauner4

2:10 PM

[syzbot] [jfs?] [nilfs?] WARNING in mnt_ns_release

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

unread,

[syzbot] [jfs?] [nilfs?] WARNING in mnt_ns_release

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

2:10 PM

1:15 PM

[syzbot] [btrfs?] kernel BUG in populate_free_space_tree

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

unread,

[syzbot] [btrfs?] kernel BUG in populate_free_space_tree

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

1:15 PM

11:53 AM

[syzbot] [btrfs?] possible deadlock in __btrfs_release_delayed_node (4)

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

unread,

[syzbot] [btrfs?] possible deadlock in __btrfs_release_delayed_node (4)

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

11:53 AM

syzbot, Hillf Danton5

10:19 AM

[syzbot] [usb?] stack segment fault in __usb_hcd_giveback_urb

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

unread,

[syzbot] [usb?] stack segment fault in __usb_hcd_giveback_urb

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

10:19 AM

8:17 AM

[syzbot] [wireless?] WARNING in mac80211_hwsim_tx

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

unread,

[syzbot] [wireless?] WARNING in mac80211_hwsim_tx

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

8:17 AM

syzbot, Hillf Danton3

4:52 AM

[syzbot] [wireless?] general protection fault in carl9170_usb_rx_complete

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

unread,

[syzbot] [wireless?] general protection fault in carl9170_usb_rx_complete

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

4:52 AM

2:51 AM

[syzbot] [bcachefs?] general protection fault in __bch2_fsck_err

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

unread,

[syzbot] [bcachefs?] general protection fault in __bch2_fsck_err

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

2:51 AM

syzbot, … Jinjiang Tu9

2:29 AM

[syzbot] [mm?] kernel BUG in try_to_unmap_one (2)

在 2025/6/6 15:56, David Hildenbrand 写道: > On 05.06.25 09:18, Jinjiang Tu wrote: >> >>

unread,

[syzbot] [mm?] kernel BUG in try_to_unmap_one (2)

在 2025/6/6 15:56, David Hildenbrand 写道: > On 05.06.25 09:18, Jinjiang Tu wrote: >> >>

2:29 AM

syzbot, … Hillf Danton6

12:22 AM

[syzbot] [mm?] WARNING in vma_modify

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

unread,

[syzbot] [mm?] WARNING in vma_modify

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

12:22 AM

12:06 AM

[syzbot] [intel-wired-lan?] WARNING in e1000_rx_checksum

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

unread,

[syzbot] [intel-wired-lan?] WARNING in e1000_rx_checksum

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

12:06 AM

Jun 6

[syzbot] [net?] divide error in taprio_update_queue_max_sdu (2)

Hello, syzbot found the following issue on: HEAD commit: 2c7e4a2663a1 Merge tag 'net-6.16-rc1

unread,

[syzbot] [net?] divide error in taprio_update_queue_max_sdu (2)

Hello, syzbot found the following issue on: HEAD commit: 2c7e4a2663a1 Merge tag 'net-6.16-rc1

Jun 6

Jun 6

[syzbot] [bcachefs?] KASAN: use-after-free Read in bkey_packed_valid

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

unread,

[syzbot] [bcachefs?] KASAN: use-after-free Read in bkey_packed_valid

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

Jun 6

Jun 6

[syzbot] [net?] WARNING: refcount bug in gro_cleanup

Hello, syzbot found the following issue on: HEAD commit: d0c22de9995b Merge tag 'input-for-v6.15-

unread,

[syzbot] [net?] WARNING: refcount bug in gro_cleanup

Hello, syzbot found the following issue on: HEAD commit: d0c22de9995b Merge tag 'input-for-v6.15-

Jun 6

Jun 6

[syzbot] [ocfs2?] possible deadlock in ocfs2_lock_refcount_tree (2)

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

unread,

[syzbot] [ocfs2?] possible deadlock in ocfs2_lock_refcount_tree (2)

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

Jun 6

Jun 6

[syzbot] [mm?] INFO: rcu detected stall in sys_unlinkat (3)

Hello, syzbot found the following issue on: HEAD commit: 92a09c47464d Linux 6.15-rc5 git tree:

unread,

[syzbot] [mm?] INFO: rcu detected stall in sys_unlinkat (3)

Hello, syzbot found the following issue on: HEAD commit: 92a09c47464d Linux 6.15-rc5 git tree:

Jun 6

syzbot, Hillf Danton5

Jun 6

[syzbot] [trace?] BUG: corrupted list in ring_buffer_subbuf_order_set

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

unread,

[syzbot] [trace?] BUG: corrupted list in ring_buffer_subbuf_order_set

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

Jun 6

syzbot, Ivan Pravdin3

Jun 6

[syzbot] [usb?] KASAN: slab-use-after-free Read in raw_event_queue_add

#syz test diff --git a/drivers/usb/gadget/legacy/raw_gadget.cb/drivers/usb/gadget/legacy/raw_gadget.c

unread,

[syzbot] [usb?] KASAN: slab-use-after-free Read in raw_event_queue_add

#syz test diff --git a/drivers/usb/gadget/legacy/raw_gadget.cb/drivers/usb/gadget/legacy/raw_gadget.c

Jun 6

syzbot, … Lizhi Xu8

Jun 6

[syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in ntfs_utf16_to_nls

The length of the file name should be smaller than the directory entry size. Reported-by: syzbot+

unread,

[syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in ntfs_utf16_to_nls

The length of the file name should be smaller than the directory entry size. Reported-by: syzbot+

Jun 6

Jun 6

[syzbot] [kernel?] KASAN: stack-out-of-bounds Write in preempt_schedule_irq

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

unread,

[syzbot] [kernel?] KASAN: stack-out-of-bounds Write in preempt_schedule_irq

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

Jun 6

Jun 5

[syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

unread,

[syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text

Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-by

Jun 5

syzbot, … Suren Baghdasaryan8

Jun 5

[syzbot] [io-uring?] [mm?] general protection fault in lock_vma_under_rcu

On Mon, May 26, 2025 at 1:50 AM syzbot <syzbot+556fda...@syzkaller.appspotmail.com>

unread,

[syzbot] [io-uring?] [mm?] general protection fault in lock_vma_under_rcu

On Mon, May 26, 2025 at 1:50 AM syzbot <syzbot+556fda...@syzkaller.appspotmail.com>

Jun 5

Jun 5

[syzbot] [xfs?] INFO: task hung in vfs_setxattr (7)

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

unread,

[syzbot] [xfs?] INFO: task hung in vfs_setxattr (7)

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

Jun 5

Jun 5

Re: [syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio

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

unread,

Re: [syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio

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

Jun 5

syzbot, … Lizhi Xu16

Jun 5

[syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio

For archival purposes, forwarding an incoming command email to linux-...@vger.kernel.org,

unread,

[syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio

For archival purposes, forwarding an incoming command email to linux-...@vger.kernel.org,

Jun 5

syzbot, Matthew Wilcox2

Jun 5

[syzbot] [ocfs2?] kernel BUG in ocfs2_write_begin_nolock (2)

On Wed, Jun 04, 2025 at 10:16:31PM -0700, syzbot wrote: > ------------[ cut here ]------------

unread,

[syzbot] [ocfs2?] kernel BUG in ocfs2_write_begin_nolock (2)

On Wed, Jun 04, 2025 at 10:16:31PM -0700, syzbot wrote: > ------------[ cut here ]------------

Jun 5

syzbot, Sean Christopherson2

Jun 5

[syzbot] [kvm-x86?] WARNING in kvm_apic_accept_events

On Thu, Jun 05, 2025, syzbot wrote: > Hello, > > syzbot found the following issue on: >

unread,

[syzbot] [kvm-x86?] WARNING in kvm_apic_accept_events

On Thu, Jun 05, 2025, syzbot wrote: > Hello, > > syzbot found the following issue on: >

Jun 5

Jun 5

[syzbot] [kernel?] WARNING in exit_itimers

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

unread,

[syzbot] [kernel?] WARNING in exit_itimers

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

Jun 5

syzbot, … Peter Zijlstra11

Jun 5

[syzbot] [mm?] possible deadlock in __vma_start_write

On Thu, Jun 05, 2025 at 11:40:04AM +0200, Petr Mladek wrote: > I just wanted to better understand

unread,

[syzbot] [mm?] possible deadlock in __vma_start_write

On Thu, Jun 05, 2025 at 11:40:04AM +0200, Petr Mladek wrote: > I just wanted to better understand

Jun 5

Jun 5

[syzbot] [block?] possible deadlock in __synchronize_srcu (2)

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

unread,

[syzbot] [block?] possible deadlock in __synchronize_srcu (2)

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

Jun 5

Search

Clear search

Close search

Google apps

Main menu