syzkaller-bugs

Contact owners and managers

1–30 of 10333

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

5:18 PM

[syzbot] [mm?] KASAN: slab-use-after-free Read in folio_evictable

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

unread,

[syzbot] [mm?] KASAN: slab-use-after-free Read in folio_evictable

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

5:18 PM

syzbot, John Fastabend2

1:38 PM

[syzbot] [net?] WARNING in tcp_recvmsg_locked (2)

syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:

unread,

[syzbot] [net?] WARNING in tcp_recvmsg_locked (2)

syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:

1:38 PM

1:25 PM

[syzbot] [net?] KMSAN: uninit-value in __llc_lookup_established

Hello, syzbot found the following issue on: HEAD commit: 1c41041124bd Merge tag 'i3c/for-6.7'

unread,

[syzbot] [net?] KMSAN: uninit-value in __llc_lookup_established

Hello, syzbot found the following issue on: HEAD commit: 1c41041124bd Merge tag 'i3c/for-6.7'

1:25 PM

11:21 AM

[syzbot] [net?] KCSAN: data-race in data_push_tail / ip6_addr_string

Hello, syzbot found the following issue on: HEAD commit: d3fa86b1a7b4 Merge tag 'net-6.7-rc3'

unread,

[syzbot] [net?] KCSAN: data-race in data_push_tail / ip6_addr_string

Hello, syzbot found the following issue on: HEAD commit: d3fa86b1a7b4 Merge tag 'net-6.7-rc3'

11:21 AM

syzbot, … Andreas Gruenbacher7

8:51 AM

[syzbot] [gfs2?] kernel BUG in gfs2_quota_cleanup

On Sat, Dec 2, 2023 at 10:34 AM Edward Adam Davis <ead...@qq.com> wrote: > [Analysis] >

unread,

[syzbot] [gfs2?] kernel BUG in gfs2_quota_cleanup

On Sat, Dec 2, 2023 at 10:34 AM Edward Adam Davis <ead...@qq.com> wrote: > [Analysis] >

8:51 AM

8:22 AM

[syzbot] [reiserfs?] kernel BUG in flush_commit_list

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

unread,

[syzbot] [reiserfs?] kernel BUG in flush_commit_list

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

8:22 AM

syzbot, … Tetsuo Handa8

7:01 AM

[syzbot] [kernel?] possible deadlock in stack_depot_put

On 2023/12/05 20:31, Hillf Danton wrote: > Unlike down_trylock(), mutex_trylock() is unable to

unread,

[syzbot] [kernel?] possible deadlock in stack_depot_put

On 2023/12/05 20:31, Hillf Danton wrote: > Unlike down_trylock(), mutex_trylock() is unable to

7:01 AM

4:53 AM

[syzbot] Monthly usb report (Dec 2023)

Hello usb maintainers/developers, This is a 31-day syzbot report for the usb subsystem. All related

unread,

[syzbot] Monthly usb report (Dec 2023)

Hello usb maintainers/developers, This is a 31-day syzbot report for the usb subsystem. All related

4:53 AM

syzbot, Hillf Danton3

4:08 AM

BUG: sleeping function called from invalid context in do_user_addr_fault (2)

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

unread,

BUG: sleeping function called from invalid context in do_user_addr_fault (2)

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

4:08 AM

syzbot, Ryusuke Konishi2

3:59 AM

[syzbot] WARNING in nilfs_sufile_set_segment_usage

If nilfs2 reads a disk image with corrupted segment usage metadata, and its segment usage information

unread,

[syzbot] WARNING in nilfs_sufile_set_segment_usage

If nilfs2 reads a disk image with corrupted segment usage metadata, and its segment usage information

3:59 AM

12:27 AM

[syzbot] [btrfs?] WARNING in btrfs_quota_enable

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

unread,

[syzbot] [btrfs?] WARNING in btrfs_quota_enable

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

12:27 AM

syzbot, Edward Adam Davis3

Dec 4

[syzbot] [net?] INFO: rcu detected stall in sys_socket (10)

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

unread,

[syzbot] [net?] INFO: rcu detected stall in sys_socket (10)

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

Dec 4

Dec 4

Re: [syzbot] [kernel?] possible deadlock in alarm_handle_timer

Hello I reproduced this bug with repro.c =* repro.txt =* r0 = syz_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0)

unread,

Re: [syzbot] [kernel?] possible deadlock in alarm_handle_timer

Hello I reproduced this bug with repro.c =* repro.txt =* r0 = syz_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0)

Dec 4

Dec 4

[syzbot] [reiserfs?] UBSAN: array-index-out-of-bounds in direntry_create_vi

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

unread,

[syzbot] [reiserfs?] UBSAN: array-index-out-of-bounds in direntry_create_vi

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

Dec 4

Dec 4

[syzbot] UBSAN: array-index-out-of-bounds in txCommit

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

unread,

[syzbot] UBSAN: array-index-out-of-bounds in txCommit

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

Dec 4

syzbot, … Aleksandr Nogikh12

Dec 4

KASAN: use-after-free Read in j1939_session_get_by_addr

This bug is marked as fixed by commit: can: j1939: transport: make sure the aborted session will be

unread,

KASAN: use-after-free Read in j1939_session_get_by_addr

This bug is marked as fixed by commit: can: j1939: transport: make sure the aborted session will be

Dec 4

Dec 4

Re: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3)

Hello I reproduced this bug with repro.c and repro.txt Because the file is relatively large, please

unread,

Re: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3)

Hello I reproduced this bug with repro.c and repro.txt Because the file is relatively large, please

Dec 4

Dec 4

[syzbot] Monthly reiserfs report (Dec 2023)

Hello reiserfs maintainers/developers, This is a 31-day syzbot report for the reiserfs subsystem. All

unread,

[syzbot] Monthly reiserfs report (Dec 2023)

Hello reiserfs maintainers/developers, This is a 31-day syzbot report for the reiserfs subsystem. All

Dec 4

Dec 4

[syzbot] Monthly jfs report (Dec 2023)

Hello jfs maintainers/developers, This is a 31-day syzbot report for the jfs subsystem. All related

unread,

[syzbot] Monthly jfs report (Dec 2023)

Hello jfs maintainers/developers, This is a 31-day syzbot report for the jfs subsystem. All related

Dec 4

Dec 4

[syzbot] Monthly bluetooth report (Dec 2023)

Hello bluetooth maintainers/developers, This is a 31-day syzbot report for the bluetooth subsystem.

unread,

[syzbot] Monthly bluetooth report (Dec 2023)

Hello bluetooth maintainers/developers, This is a 31-day syzbot report for the bluetooth subsystem.

Dec 4

Dec 4

Re: [syzbot] [bpf?] [trace?] possible deadlock in dev_watchdog

hello I reproduced this bug with repro.c and repro.txt =* repro.txt =* r0 = syz_clone(0x0, 0x0, 0x0,

unread,

Re: [syzbot] [bpf?] [trace?] possible deadlock in dev_watchdog

hello I reproduced this bug with repro.c and repro.txt =* repro.txt =* r0 = syz_clone(0x0, 0x0, 0x0,

Dec 4

Dec 4

[syzbot] [net?] INFO: rcu detected stall in ip_list_rcv (6)

Hello, syzbot found the following issue on: HEAD commit: 753c8608f3e5 Merge tag 'for-netdev'

unread,

[syzbot] [net?] INFO: rcu detected stall in ip_list_rcv (6)

Hello, syzbot found the following issue on: HEAD commit: 753c8608f3e5 Merge tag 'for-netdev'

Dec 4

Dec 4

[syzbot] [hfs?] KASAN: invalid-free in hfs_release_folio

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

unread,

[syzbot] [hfs?] KASAN: invalid-free in hfs_release_folio

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

Dec 4

Lizhi Xu, … syzbot32

Dec 3

[PATCH] test aea6bf908d73

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

unread,

[PATCH] test aea6bf908d73

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

Dec 3

syzbot, Hillf Danton5

Dec 3

[syzbot] [net?] INFO: rcu detected stall in rtnl_newlink (3)

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

unread,

[syzbot] [net?] INFO: rcu detected stall in rtnl_newlink (3)

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

Dec 3

syzbot, Johannes Berg4

Dec 3

[syzbot] [wireless?] WARNING in ieee80211_link_release_channel

syzbot suspects this issue was fixed by commit: commit 88717def36f7b19f12d6ad6644e73bf91cf86375

unread,

[syzbot] [wireless?] WARNING in ieee80211_link_release_channel

syzbot suspects this issue was fixed by commit: commit 88717def36f7b19f12d6ad6644e73bf91cf86375

Dec 3

syzbot, … Pengfei Xu13

Dec 3

[syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4)

Hi, On 2023-12-03 at 06:07:43 +0800, Steven Rostedt wrote: > On Sat, 2 Dec 2023 17:19:25 +0800

unread,

[syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4)

Hi, On 2023-12-03 at 06:07:43 +0800, Steven Rostedt wrote: > On Sat, 2 Dec 2023 17:19:25 +0800

Dec 3

Dec 3

[syzbot] [kernfs?] possible deadlock in walk_component (2)

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

unread,

[syzbot] [kernfs?] possible deadlock in walk_component (2)

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

Dec 3

Dec 3

[syzbot] [ntfs3?] kernel BUG in __blockdev_direct_IO

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

unread,

[syzbot] [ntfs3?] kernel BUG in __blockdev_direct_IO

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

Dec 3

Dec 3

[syzbot] [nilfs?] WARNING in nilfs_btree_assign (2)

Hello, syzbot found the following issue on: HEAD commit: 18d46e76d7c2 Merge tag 'for-6.7-rc3-tag

unread,

[syzbot] [nilfs?] WARNING in nilfs_btree_assign (2)

Hello, syzbot found the following issue on: HEAD commit: 18d46e76d7c2 Merge tag 'for-6.7-rc3-tag

Dec 3

Search

Clear search

Close search

Google apps

Main menu