Groups

syzkaller-bugs

Contact owners and managers

1–30 of 16721

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

7:59 AM

[syzbot] Monthly wpan report (Feb 2026)

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

unread,

[syzbot] Monthly wpan report (Feb 2026)

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

7:59 AM

7:58 AM

[syzbot] Monthly hams report (Feb 2026)

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

unread,

[syzbot] Monthly hams report (Feb 2026)

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

7:58 AM

7:58 AM

[syzbot] Monthly netfilter report (Feb 2026)

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

unread,

[syzbot] Monthly netfilter report (Feb 2026)

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

7:58 AM

7:58 AM

[syzbot] Monthly jfs report (Feb 2026)

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

unread,

[syzbot] Monthly jfs report (Feb 2026)

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

7:58 AM

7:58 AM

[syzbot] Monthly kernfs report (Feb 2026)

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

unread,

[syzbot] Monthly kernfs report (Feb 2026)

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

7:58 AM

syzbot, … Hillf Danton26

5:50 AM

[syzbot] [kernel?] INFO: task hung in restrict_one_thread_callback

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

unread,

[syzbot] [kernel?] INFO: task hung in restrict_one_thread_callback

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

5:50 AM

syzbot, Qing Wang7

4:43 AM

[syzbot] [trace?] WARNING in tracing_buffers_mmap_close (3)

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

unread,

[syzbot] [trace?] WARNING in tracing_buffers_mmap_close (3)

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

4:43 AM

4:36 AM

[syzbot] [ext4?] INFO: task hung in block_read_full_folio (3)

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

unread,

[syzbot] [ext4?] INFO: task hung in block_read_full_folio (3)

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

4:36 AM

4:31 AM

[syzbot ci] Re: Close race in freeing special fields and map value

syzbot ci has tested the following series [v1] Close race in freeing special fields and map value

unread,

[syzbot ci] Re: Close race in freeing special fields and map value

syzbot ci has tested the following series [v1] Close race in freeing special fields and map value

4:31 AM

3:31 AM

[syzbot] [serial?] KASAN: slab-out-of-bounds Write in do_con_write (3)

Hello, syzbot found the following issue on: HEAD commit: d9d32e5bd5a4 Merge tag 'ata-7.0-rc2'

unread,

[syzbot] [serial?] KASAN: slab-out-of-bounds Write in do_con_write (3)

Hello, syzbot found the following issue on: HEAD commit: d9d32e5bd5a4 Merge tag 'ata-7.0-rc2'

3:31 AM

1:18 AM

[syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (6)

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

unread,

[syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (6)

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

1:18 AM

1:07 AM

[syzbot] [kernfs?] possible deadlock in __kernfs_remove (3)

Hello, syzbot found the following issue on: HEAD commit: d4f687fbbce4 ovpn: tcp - fix packet

unread,

[syzbot] [kernfs?] possible deadlock in __kernfs_remove (3)

Hello, syzbot found the following issue on: HEAD commit: d4f687fbbce4 ovpn: tcp - fix packet

1:07 AM

12:20 AM

[syzbot] [bpf?] linux-next test error: WARNING: kmalloc bug in bpf_prog_alloc_no_stats

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

unread,

[syzbot] [bpf?] linux-next test error: WARNING: kmalloc bug in bpf_prog_alloc_no_stats

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

12:20 AM

Feb 25

[syzbot] [net?] [virt?] [kvm?] BUG: soft lockup in vsock_loopback_work

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

unread,

[syzbot] [net?] [virt?] [kvm?] BUG: soft lockup in vsock_loopback_work

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

Feb 25

Feb 25

[syzbot] [wireless?] WARNING in ieee80211_set_active_links (3)

Hello, syzbot found the following issue on: HEAD commit: 7dff99b35460 Remove WARN_ALL_UNSEEDED_RANDOM

unread,

[syzbot] [wireless?] WARNING in ieee80211_set_active_links (3)

Hello, syzbot found the following issue on: HEAD commit: 7dff99b35460 Remove WARN_ALL_UNSEEDED_RANDOM

Feb 25

syzbot, … Sean Christopherson4

Feb 25

[syzbot] [kvm?] WARNING in kvm_read_guest_offset_cached

On Tue, Feb 10, 2026, Alexander Potapenko wrote: > On Wed, Jul 16, 2025 at 5:23 PM 'Sean

unread,

[syzbot] [kvm?] WARNING in kvm_read_guest_offset_cached

On Tue, Feb 10, 2026, Alexander Potapenko wrote: > On Wed, Jul 16, 2025 at 5:23 PM 'Sean

Feb 25

Feb 25

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

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

unread,

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

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

Feb 25

Feb 25

Re: [syzbot] [jfs?] general protection fault in lmLogSync (2)

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

unread,

Re: [syzbot] [jfs?] general protection fault in lmLogSync (2)

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

Feb 25

Feb 25

[syzbot] general protection fault in lmLogSync (2)

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

unread,

[syzbot] general protection fault in lmLogSync (2)

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

Feb 25

syzbot, Heitor Alves de Siqueira9

Feb 25

[syzbot] [batman?] [bluetooth?] memory leak in skb_clone (3)

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

unread,

[syzbot] [batman?] [bluetooth?] memory leak in skb_clone (3)

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

Feb 25

Feb 25

[syzbot] [wireless?] WARNING in ieee80211_tx_monitor (3)

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

unread,

[syzbot] [wireless?] WARNING in ieee80211_tx_monitor (3)

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

Feb 25

Feb 25

[syzbot] [comedi?] inconsistent lock state in waveform_ao_cancel

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

unread,

[syzbot] [comedi?] inconsistent lock state in waveform_ao_cancel

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

Feb 25

Feb 25

[syzbot] [net?] [bpf?] KCSAN: data-race in sk_psock_drop / unix_stream_sendmsg

Hello, syzbot found the following issue on: HEAD commit: 23b0f90ba871 Merge tag 'sysctl-7.00-rc1

unread,

[syzbot] [net?] [bpf?] KCSAN: data-race in sk_psock_drop / unix_stream_sendmsg

Hello, syzbot found the following issue on: HEAD commit: 23b0f90ba871 Merge tag 'sysctl-7.00-rc1

Feb 25

Feb 25

[syzbot] [bluetooth?] linux-next test error: KASAN: slab-use-after-free Read in hci_cmd_work

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

unread,

[syzbot] [bluetooth?] linux-next test error: KASAN: slab-use-after-free Read in hci_cmd_work

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

Feb 25

syzbot, … Ian Abbott3

Feb 25

[syzbot] [kernel?] WARNING in request_threaded_irq

On 24/02/2026 18:24, Thomas Gleixner wrote: > On Fri, Feb 20 2026 at 05:13, syzbot wrote: >

unread,

[syzbot] [kernel?] WARNING in request_threaded_irq

On 24/02/2026 18:24, Thomas Gleixner wrote: > On Fri, Feb 20 2026 at 05:13, syzbot wrote: >

Feb 25

Feb 25

[syzbot] [bpf?] WARNING: kmalloc bug in bpf_prog_alloc_no_stats

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

unread,

[syzbot] [bpf?] WARNING: kmalloc bug in bpf_prog_alloc_no_stats

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

Feb 25

Feb 25

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

Hello, syzbot found the following issue on: HEAD commit: a95f71ad3e2e Merge tag 'for-linus'

unread,

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

Hello, syzbot found the following issue on: HEAD commit: a95f71ad3e2e Merge tag 'for-linus'

Feb 25

Mauricio Faria de Oliveira3

Feb 25

KASAN: slab-use-after-free Write in number

#syz fix: media: mc: fix potential use-after-free in media_request_alloc() -- Mauricio

unread,

KASAN: slab-use-after-free Write in number

#syz fix: media: mc: fix potential use-after-free in media_request_alloc() -- Mauricio

Feb 25

Feb 25

[syzbot] [kernel?] INFO: task hung in rxrpc_destroy_all_connections (5)

Hello, syzbot found the following issue on: HEAD commit: 7dff99b35460 Remove WARN_ALL_UNSEEDED_RANDOM

unread,

[syzbot] [kernel?] INFO: task hung in rxrpc_destroy_all_connections (5)

Hello, syzbot found the following issue on: HEAD commit: 7dff99b35460 Remove WARN_ALL_UNSEEDED_RANDOM

Feb 25

syzbot, Hillf Danton3

Feb 25

[syzbot] [usb?] BUG: sleeping function called from invalid context in usb_tx_block

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

unread,

[syzbot] [usb?] BUG: sleeping function called from invalid context in usb_tx_block

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

Feb 25

Search

Clear search

Close search

Google apps

Main menu