Groups

syzkaller-bugs

Contact owners and managers

1–30 of 16581

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 ci, syzbot ci2

6:02 AM

[syzbot ci] Re: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap

syzbot ci has tested the following series [v3] bpf: test_run: Fix the null pointer dereference issue

unread,

[syzbot ci] Re: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap

syzbot ci has tested the following series [v3] bpf: test_run: Fix the null pointer dereference issue

6:02 AM

syzbot, … Peter Zijlstra4

5:33 AM

[syzbot] [perf?] KCSAN: data-race in perf_event_set_state / perf_mmap_rb

On Fri, Feb 06, 2026 at 10:18:38AM +0100, Peter Zijlstra wrote: > > Because `perf_mmap_rb()`

unread,

[syzbot] [perf?] KCSAN: data-race in perf_event_set_state / perf_mmap_rb

On Fri, Feb 06, 2026 at 10:18:38AM +0100, Peter Zijlstra wrote: > > Because `perf_mmap_rb()`

5:33 AM

4:51 AM

[BUG] KASAN_ null-ptr-deref in h5_recv during HCI UART handling on Linux 6.18

Dear Maintainers, When using our customized Syzkaller to fuzz the latest Linux kernel, the following

unread,

[BUG] KASAN_ null-ptr-deref in h5_recv during HCI UART handling on Linux 6.18

Dear Maintainers, When using our customized Syzkaller to fuzz the latest Linux kernel, the following

4:51 AM

4:24 AM

[syzbot] [afs?] KASAN: slab-use-after-free Read in __radix_tree_replace

Hello, syzbot found the following issue on: HEAD commit: d358e5254674 Merge tag 'for-6.19/dm-

unread,

[syzbot] [afs?] KASAN: slab-use-after-free Read in __radix_tree_replace

Hello, syzbot found the following issue on: HEAD commit: d358e5254674 Merge tag 'for-6.19/dm-

4:24 AM

syzbot, … Peter Zijlstra3

4:16 AM

[syzbot] [perf?] KCSAN: data-race in __perf_event_read_value / perf_event_set_state (6)

On Fri, Feb 06, 2026 at 08:37:14AM +0100, Dmitry Vyukov wrote: > On Fri, 6 Feb 2026 at 08:34,

unread,

[syzbot] [perf?] KCSAN: data-race in __perf_event_read_value / perf_event_set_state (6)

On Fri, Feb 06, 2026 at 08:37:14AM +0100, Dmitry Vyukov wrote: > On Fri, 6 Feb 2026 at 08:34,

4:16 AM

syzbot, Prithvi Tambewagh7

4:04 AM

[syzbot] [fs?] possible deadlock in __configfs_open_file

Hello, syzbot tried to test the proposed patch but the build/boot failed: failed to run ["make

unread,

[syzbot] [fs?] possible deadlock in __configfs_open_file

Hello, syzbot tried to test the proposed patch but the build/boot failed: failed to run ["make

4:04 AM

3:32 AM

[syzbot ci] Re: net/rds: RDS-TCP reconnect and fanout improvements

syzbot ci has tested the following series [v1] net/rds: RDS-TCP reconnect and fanout improvements

unread,

[syzbot ci] Re: net/rds: RDS-TCP reconnect and fanout improvements

syzbot ci has tested the following series [v1] net/rds: RDS-TCP reconnect and fanout improvements

3:32 AM

3:32 AM

[syzbot ci] Re: net: sched: refactor qdisc drop reasons into dedicated tracepoint

syzbot ci has tested the following series [v2] net: sched: refactor qdisc drop reasons into dedicated

unread,

[syzbot ci] Re: net: sched: refactor qdisc drop reasons into dedicated tracepoint

syzbot ci has tested the following series [v2] net: sched: refactor qdisc drop reasons into dedicated

3:32 AM

syzbot, … OGAWA Hirofumi3

2:40 AM

[syzbot] [exfat?] KCSAN: data-race in fat12_ent_put / fat_mirror_bhs

syzbot <syzbot+51b4c6...@syzkaller.appspotmail.com> writes: > Hello, > >

unread,

[syzbot] [exfat?] KCSAN: data-race in fat12_ent_put / fat_mirror_bhs

syzbot <syzbot+51b4c6...@syzkaller.appspotmail.com> writes: > Hello, > >

2:40 AM

syzbot, Dmitry Vyukov2

2:31 AM

[syzbot] [cgroups?] [mm?] KASAN: wild-memory-access Read in lookup_swap_cgroup_id (2)

On Fri, 6 Feb 2026 at 08:24, syzbot <syzbot+e12bd9...@syzkaller.appspotmail.com>

unread,

[syzbot] [cgroups?] [mm?] KASAN: wild-memory-access Read in lookup_swap_cgroup_id (2)

On Fri, 6 Feb 2026 at 08:24, syzbot <syzbot+e12bd9...@syzkaller.appspotmail.com>

2:31 AM

syzbot, … Edward Adam Davis8

1:53 AM

[syzbot] [fuse?] KMSAN: uninit-value in fuse_fileattr_get

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

unread,

[syzbot] [fuse?] KMSAN: uninit-value in fuse_fileattr_get

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

1:53 AM

syzbot, Dmitry Vyukov2

1:31 AM

[syzbot] [smc?] KCSAN: data-race in smc_switch_to_fallback / sock_poll (2)

On Fri, 6 Feb 2026 at 07:16, syzbot <syzbot+198c20...@syzkaller.appspotmail.com>

unread,

[syzbot] [smc?] KCSAN: data-race in smc_switch_to_fallback / sock_poll (2)

On Fri, 6 Feb 2026 at 07:16, syzbot <syzbot+198c20...@syzkaller.appspotmail.com>

1:31 AM

Feb 5

[syzbot] [net?] [usb?] WARNING: ODEBUG bug in trace_suspend_resume

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

unread,

[syzbot] [net?] [usb?] WARNING: ODEBUG bug in trace_suspend_resume

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

Feb 5

Feb 5

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

Hello, syzbot found the following issue on: HEAD commit: 099ba40b1bd9 riscv: lib: optimize strlen

unread,

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

Hello, syzbot found the following issue on: HEAD commit: 099ba40b1bd9 riscv: lib: optimize strlen

Feb 5

syzbot, John Hubbard2

Feb 5

[syzbot] [mm?] possible deadlock in gup_fast_fallback (2)

#syz fix: procfs: avoid fetching build ID while holding VMA lock On 2/5/26 1:44 PM, syzbot wrote:

unread,

[syzbot] [mm?] possible deadlock in gup_fast_fallback (2)

#syz fix: procfs: avoid fetching build ID while holding VMA lock On 2/5/26 1:44 PM, syzbot wrote:

Feb 5

Feb 5

[syzbot] [kernel?] WARNING in __run_timer_base

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

unread,

[syzbot] [kernel?] WARNING in __run_timer_base

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

Feb 5

Feb 5

[syzbot] [f2fs?] kernel BUG in clear_inode (5)

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

unread,

[syzbot] [f2fs?] kernel BUG in clear_inode (5)

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

Feb 5

Feb 5

[syzbot] Monthly f2fs report (Feb 2026)

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

unread,

[syzbot] Monthly f2fs report (Feb 2026)

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

Feb 5

Feb 5

[syzbot] Monthly ocfs2 report (Feb 2026)

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

unread,

[syzbot] Monthly ocfs2 report (Feb 2026)

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

Feb 5

syzbot, Qing Wang5

Feb 5

[syzbot] [gfs2?] memory leak in gfs2_quota_init (2)

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

unread,

[syzbot] [gfs2?] memory leak in gfs2_quota_init (2)

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

Feb 5

syzbot, … Anton Protopopov5

Feb 5

[syzbot] [bpf?] WARNING: refcount bug in __add_used_btf

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

unread,

[syzbot] [bpf?] WARNING: refcount bug in __add_used_btf

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

Feb 5

syzbot, Gao Xiang4

Feb 5

[syzbot] [erofs?] WARNING in erofs_iget (2)

On 2026/2/5 10:27, syzbot wrote: > Hello, > > syzbot has tested the proposed patch and the

unread,

[syzbot] [erofs?] WARNING in erofs_iget (2)

On 2026/2/5 10:27, syzbot wrote: > Hello, > > syzbot has tested the proposed patch and the

Feb 5

Feb 4

[syzbot] [wireless?] WARNING in rfkill_fop_open

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

unread,

[syzbot] [wireless?] WARNING in rfkill_fop_open

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

Feb 4

syzbot, … Ackerley Tng21

Feb 4

[syzbot] [kvm?] WARNING in kvm_gmem_fault_user_mapping

"David Hildenbrand (arm)" <da...@kernel.org> writes: > On 2/4/26 22:37, Sean

unread,

[syzbot] [kvm?] WARNING in kvm_gmem_fault_user_mapping

"David Hildenbrand (arm)" <da...@kernel.org> writes: > On 2/4/26 22:37, Sean

Feb 4

Feb 4

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

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

unread,

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

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

Feb 4

syzbot, Andreas Gruenbacher11

Feb 4

[syzbot] [gfs2?] memory leak in __kthread_create_on_node

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

unread,

[syzbot] [gfs2?] memory leak in __kthread_create_on_node

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

Feb 4

Ackerley Tng, Deepanshu Kartikey3

Feb 4

[PATCH 1/2] KVM: guest_memfd: Always use order 0 when allocating for guest_memfd

Deepanshu Kartikey <karti...@gmail.com> writes: > On Wed, Feb 4, 2026 at 4:21 AM Ackerley

unread,

[PATCH 1/2] KVM: guest_memfd: Always use order 0 when allocating for guest_memfd

Deepanshu Kartikey <karti...@gmail.com> writes: > On Wed, Feb 4, 2026 at 4:21 AM Ackerley

Feb 4

Shigeru Yoshida, syzbot2

Feb 4

Test for cb809def1baaac68ab92

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

unread,

Test for cb809def1baaac68ab92

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

Feb 4

Feb 4

[syzbot ci] Re: KVM: VMX APIC timer virtualization support

syzbot ci has tested the following series [v1] KVM: VMX APIC timer virtualization support https://

unread,

[syzbot ci] Re: KVM: VMX APIC timer virtualization support

syzbot ci has tested the following series [v1] KVM: VMX APIC timer virtualization support https://

Feb 4

Feb 4

[syzbot] [i2c?] WARNING: refcount bug in i2c_get_adapter

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

unread,

[syzbot] [i2c?] WARNING: refcount bug in i2c_get_adapter

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

Feb 4

Search

Clear search

Close search

Google apps

Main menu