Groups

syzkaller-bugs

Contact owners and managers

1–30 of 17165

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, … Andrew Morton4

1:55 PM

[syzbot] [mm?] WARNING: bad unlock balance in do_wp_page

On Sun, 26 Apr 2026 23:57:42 +0800 Qi Zheng <qi.z...@linux.dev> wrote: > Hi Andrew, >

unread,

[syzbot] [mm?] WARNING: bad unlock balance in do_wp_page

On Sun, 26 Apr 2026 23:57:42 +0800 Qi Zheng <qi.z...@linux.dev> wrote: > Hi Andrew, >

1:55 PM

4:16 AM

[syzbot] [net?] kernel BUG in pn_socket_autobind

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

unread,

[syzbot] [net?] kernel BUG in pn_socket_autobind

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

4:16 AM

syzbot, Edward Adam Davis4

1:33 AM

[syzbot] [media?] memory leak in dvb_dmxdev_add_pid

The user first executes set pes filter to create a PID, and subsequently executes set filter to sec.

unread,

[syzbot] [media?] memory leak in dvb_dmxdev_add_pid

The user first executes set pes filter to create a PID, and subsequently executes set filter to sec.

1:33 AM

12:42 AM

[syzbot] [input?] possible deadlock in tasklet_action_common

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

unread,

[syzbot] [input?] possible deadlock in tasklet_action_common

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

12:42 AM

Apr 25

Re: [BUG] ext4: BUG_ON in ext4_write_inline_data (fs/ext4/inline.c:240)

On Sat, Apr 25, 2026 at 02:00:23PM -0400, Demi Marie Obenour wrote: > > Changing block devices

unread,

Re: [BUG] ext4: BUG_ON in ext4_write_inline_data (fs/ext4/inline.c:240)

On Sat, Apr 25, 2026 at 02:00:23PM -0400, Demi Marie Obenour wrote: > > Changing block devices

Apr 25

syzbot, Hillf Danton14

Apr 25

[syzbot] [usb?] memory leak in hub_event (4)

> Date: Sat, 25 Apr 2026 07:43:17 -0700 > For archival purposes, forwarding an incoming command

unread,

[syzbot] [usb?] memory leak in hub_event (4)

> Date: Sat, 25 Apr 2026 07:43:17 -0700 > For archival purposes, forwarding an incoming command

Apr 25

Apr 25

[syzbot] [bluetooth?] WARNING in hci_send_cmd (4)

Hello, syzbot found the following issue on: HEAD commit: b4e07588e743 tracing: tell git to ignore the

unread,

[syzbot] [bluetooth?] WARNING in hci_send_cmd (4)

Hello, syzbot found the following issue on: HEAD commit: b4e07588e743 tracing: tell git to ignore the

Apr 25

syzbot, Arjan van de Ven2

Apr 25

[syzbot] [i2c?] WARNING: refcount bug in i2c_get_adapter (2)

This email is created by automation to help kernel developers deal with a large volume of AI

unread,

[syzbot] [i2c?] WARNING: refcount bug in i2c_get_adapter (2)

This email is created by automation to help kernel developers deal with a large volume of AI

Apr 25

Apr 25

[syzbot] [mm?] WARNING: bad unlock balance in folios_put_refs

> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git This crash does

unread,

[syzbot] [mm?] WARNING: bad unlock balance in folios_put_refs

> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git This crash does

Apr 25

syzbot, … Lance Yang5

Apr 25

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

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

unread,

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

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

Apr 25

Apr 25

[syzbot] [btrfs] possible deadlock in page_cache_ra_unbounded (3)

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

unread,

[syzbot] [btrfs] possible deadlock in page_cache_ra_unbounded (3)

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

Apr 25

Apr 25

[syzbot] [mm?] KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)

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

unread,

[syzbot] [mm?] KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)

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

Apr 25

Apr 25

[syzbot] [fs?] [mm?] [io-uring?] INFO: task hung in hugetlbfs_zero_partial_page

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

unread,

[syzbot] [fs?] [mm?] [io-uring?] INFO: task hung in hugetlbfs_zero_partial_page

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

Apr 25

syzbot, … Edward Adam Davis7

Apr 25

[syzbot] [isdn4linux?] [nilfs?] INFO: task hung in mISDN_ioctl

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

unread,

[syzbot] [isdn4linux?] [nilfs?] INFO: task hung in mISDN_ioctl

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

Apr 25

Apr 25

[syzbot] [mm?] WARNING: lock held when returning to user space in __pte_offset_map

Hello, syzbot found the following issue on: HEAD commit: dd6c438c3e64 Merge tag 'vfs-7.1-rc1.

unread,

[syzbot] [mm?] WARNING: lock held when returning to user space in __pte_offset_map

Hello, syzbot found the following issue on: HEAD commit: dd6c438c3e64 Merge tag 'vfs-7.1-rc1.

Apr 25

Apr 25

[syzbot] [wireless?] WARNING in drv_get_tsf (2)

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

unread,

[syzbot] [wireless?] WARNING in drv_get_tsf (2)

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

Apr 25

Apr 24

[syzbot] [block?] possible deadlock in bioset_exit

Hello, syzbot found the following issue on: HEAD commit: dd6c438c3e64 Merge tag 'vfs-7.1-rc1.

unread,

[syzbot] [block?] possible deadlock in bioset_exit

Hello, syzbot found the following issue on: HEAD commit: dd6c438c3e64 Merge tag 'vfs-7.1-rc1.

Apr 24

Apr 24

[syzbot] [ocfs2?] possible deadlock in ocfs2_evict_inode

syzbot has found a reproducer for the following issue on: HEAD commit: dd6c438c3e64 Merge tag '

unread,

[syzbot] [ocfs2?] possible deadlock in ocfs2_evict_inode

syzbot has found a reproducer for the following issue on: HEAD commit: dd6c438c3e64 Merge tag '

Apr 24

Apr 24

[syzbot ci] Re: vsock/virtio: fix memory leak in virtio_transport_recv_listen()

syzbot ci has tested the following series [v1] vsock/virtio: fix memory leak in

unread,

[syzbot ci] Re: vsock/virtio: fix memory leak in virtio_transport_recv_listen()

syzbot ci has tested the following series [v1] vsock/virtio: fix memory leak in

Apr 24

Apr 24

[syzbot] [mm?] WARNING: bad unlock balance in __zap_vma_range

Hello, syzbot found the following issue on: HEAD commit: c1f49dea2b8f Merge tag 'mm-hotfixes-

unread,

[syzbot] [mm?] WARNING: bad unlock balance in __zap_vma_range

Hello, syzbot found the following issue on: HEAD commit: c1f49dea2b8f Merge tag 'mm-hotfixes-

Apr 24

syzbot, Christian Brauner5

Apr 24

[syzbot] [fs?] possible deadlock in put_mnt_ns

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

unread,

[syzbot] [fs?] possible deadlock in put_mnt_ns

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

Apr 24

syzbot, … Arjan van de Ven4

Apr 24

[syzbot] [net?] general protection fault in kernel_sock_shutdown (4)

Unfortunately the AI had a burp and did not write out the proper URL for analysis data; it should

unread,

[syzbot] [net?] general protection fault in kernel_sock_shutdown (4)

Unfortunately the AI had a burp and did not write out the proper URL for analysis data; it should

Apr 24

syzbot, ar...@linux.intel.com2

Apr 24

[syzbot] [btrfs?] WARNING in __btrfs_update_delayed_inode (4)

From: Arjan van de Ven <ar...@linux.intel.com> On Fri, 24 Apr 2026 00:54:32 -0700 syzbot <

unread,

[syzbot] [btrfs?] WARNING in __btrfs_update_delayed_inode (4)

From: Arjan van de Ven <ar...@linux.intel.com> On Fri, 24 Apr 2026 00:54:32 -0700 syzbot <

Apr 24

syzbot, … Andrew Morton3

Apr 24

[syzbot] [mm?] BUG: sleeping function called from invalid context in shmem_undo_range

On Thu, 23 Apr 2026 19:34:54 -0700 Arjan van de Ven <ar...@linux.intel.com> wrote: > This

unread,

[syzbot] [mm?] BUG: sleeping function called from invalid context in shmem_undo_range

On Thu, 23 Apr 2026 19:34:54 -0700 Arjan van de Ven <ar...@linux.intel.com> wrote: > This

Apr 24

Deepanshu Kartikey, … Rémi Denis-Courmont6

Apr 24

Re: [PATCH] net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind

Le 23 avril 2026 04:05:57 GMT+03:00, Morduan Zang <zhang...@uniontech.com> a écrit : >

unread,

Re: [PATCH] net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind

Le 23 avril 2026 04:05:57 GMT+03:00, Morduan Zang <zhang...@uniontech.com> a écrit : >

Apr 24

Apr 24

[syzbot ci] Re: mm/lruvec: preemptively free dead folios during lru_add drain

syzbot ci has tested the following series [v1] mm/lruvec: preemptively free dead folios during

unread,

[syzbot ci] Re: mm/lruvec: preemptively free dead folios during lru_add drain

syzbot ci has tested the following series [v1] mm/lruvec: preemptively free dead folios during

Apr 24

Apr 24

[syzbot ci] Re: netlink: clean up failed initial dump-start state

syzbot ci has tested the following series [v2] netlink: clean up failed initial dump-start state

unread,

[syzbot ci] Re: netlink: clean up failed initial dump-start state

syzbot ci has tested the following series [v2] netlink: clean up failed initial dump-start state

Apr 24

Apr 24

[syzbot] [virt?] [net?] memory leak in __vsock_create (2)

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

unread,

[syzbot] [virt?] [net?] memory leak in __vsock_create (2)

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

Apr 24

Apr 23

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

Hello, syzbot found the following issue on: HEAD commit: bea8d77e45a8 Merge tag 'staging-7.1-rc1

unread,

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

Hello, syzbot found the following issue on: HEAD commit: bea8d77e45a8 Merge tag 'staging-7.1-rc1

Apr 23

Apr 23

[syzbot] [wireless?] [usb?] KASAN: stack-out-of-bounds Write in carl9170_handle_command_response

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

unread,

[syzbot] [wireless?] [usb?] KASAN: stack-out-of-bounds Write in carl9170_handle_command_response

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

Apr 23

Search

Clear search

Close search

Google apps

Main menu