Groups

syzkaller-bugs

Contact owners and managers

1–30 of 16739

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:12 PM

[syzbot ci] Re: l2tp: account for IP version in SKB headroom

syzbot ci has tested the following series [v1] l2tp: account for IP version in SKB headroom https://

unread,

[syzbot ci] Re: l2tp: account for IP version in SKB headroom

syzbot ci has tested the following series [v1] l2tp: account for IP version in SKB headroom https://

5:12 PM

11:11 AM

[syzbot] [kernel?] WARNING in do_notify_parent

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

unread,

[syzbot] [kernel?] WARNING in do_notify_parent

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

11:11 AM

syzbot, Marc Zyngier3

10:57 AM

[syzbot] [kvmarm?] [kvm?] BUG: unable to handle kernel paging request in kvm_vgic_destroy

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

unread,

[syzbot] [kvmarm?] [kvm?] BUG: unable to handle kernel paging request in kvm_vgic_destroy

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

10:57 AM

10:34 AM

[syzbot] [kernel?] possible deadlock in device_create (2)

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

unread,

[syzbot] [kernel?] possible deadlock in device_create (2)

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

10:34 AM

syzbot, Tetsuo Handa2

7:53 AM

[syzbot] [rdma?] kernel BUG in ib_device_get_by_netdev

unread,

[syzbot] [rdma?] kernel BUG in ib_device_get_by_netdev

7:53 AM

6:46 AM

[syzbot] [kernel?] KMSAN: uninit-value in psi_group_change

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

unread,

[syzbot] [kernel?] KMSAN: uninit-value in psi_group_change

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

6:46 AM

6:20 AM

[syzbot ci] Re: mm: bail out when the PMD has been set in bloom filter

syzbot ci has tested the following series [v1] mm: bail out when the PMD has been set in bloom filter

unread,

[syzbot ci] Re: mm: bail out when the PMD has been set in bloom filter

syzbot ci has tested the following series [v1] mm: bail out when the PMD has been set in bloom filter

6:20 AM

syzbot, Qing Wang4

4:45 AM

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

On Sat, 28 Feb 2026 at 16:29, Qing Wang <wangqi...@gmail.com> wrote: > #syz test >

unread,

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

On Sat, 28 Feb 2026 at 16:29, Qing Wang <wangqi...@gmail.com> wrote: > #syz test >

4:45 AM

syzbot, Hillf Danton4

12:14 AM

[syzbot] [libertas?] INFO: task hung in lbs_remove_card

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

unread,

[syzbot] [libertas?] INFO: task hung in lbs_remove_card

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

12:14 AM

syzbot, Tetsuo Handa2

12:07 AM

[syzbot] [rdma?] kernel BUG in ib_device_get_by_index

Hmm, this assertion was wrong because ib_device_get_by_index() might be called before

unread,

[syzbot] [rdma?] kernel BUG in ib_device_get_by_index

Hmm, this assertion was wrong because ib_device_get_by_index() might be called before

12:07 AM

syzbot ci, yebin (H)2

Feb 27

[syzbot ci] Re: ext4: test if inode's all dirty pages are submitted to disk

This is my oversight. If the file system has already become read-only and dirty pages cannot be

unread,

[syzbot ci] Re: ext4: test if inode's all dirty pages are submitted to disk

This is my oversight. If the file system has already become read-only and dirty pages cannot be

Feb 27

Feb 27

[syzbot] [ext4?] INFO: task hung in ext4_map_blocks (5)

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

unread,

[syzbot] [ext4?] INFO: task hung in ext4_map_blocks (5)

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

Feb 27

Feb 27

[syzbot] [wireless?] KASAN: slab-use-after-free Read in __ieee80211_beacon_add_tim

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

unread,

[syzbot] [wireless?] KASAN: slab-use-after-free Read in __ieee80211_beacon_add_tim

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

Feb 27

Feb 27

[syzbot ci] Re: BIG TCP for UDP tunnels

syzbot ci has tested the following series [v2] BIG TCP for UDP tunnels https://lore.kernel.org/all/

unread,

[syzbot ci] Re: BIG TCP for UDP tunnels

syzbot ci has tested the following series [v2] BIG TCP for UDP tunnels https://lore.kernel.org/all/

Feb 27

Feb 27

[syzbot] [wireless?] divide error in mac80211_hwsim_link_info_changed (2)

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

unread,

[syzbot] [wireless?] divide error in mac80211_hwsim_link_info_changed (2)

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

Feb 27

syzbot, … syzbot10

Feb 27

[syzbot] general protection fault in lmLogSync (2)

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

unread,

[syzbot] general protection fault in lmLogSync (2)

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

Feb 27

Feb 27

Re: [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9)

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

unread,

Re: [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9)

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

Feb 27

Feb 27

[syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9)

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

unread,

[syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9)

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

Feb 27

syzbot, Andrew Price4

Feb 27

[syzbot] [gfs2?] kernel BUG in gfs2_withdraw (2)

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

unread,

[syzbot] [gfs2?] kernel BUG in gfs2_withdraw (2)

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

Feb 27

syzbot, Roberto A. Foglietta2

Feb 27

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

> On Wednesday, 25 February 2026 at 08:45:32 UTC+1 syzbot wrote: > > Hello, > > syzbot

unread,

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

> On Wednesday, 25 February 2026 at 08:45:32 UTC+1 syzbot wrote: > > Hello, > > syzbot

Feb 27

Feb 27

[syzbot] [wireless?] possible deadlock in ieee80211_change_mac (4)

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

unread,

[syzbot] [wireless?] possible deadlock in ieee80211_change_mac (4)

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

Feb 27

syzbot, Qing Wang5

Feb 27

[syzbot] [bpf?] [trace?] KASAN: slab-use-after-free Read in bpf_trace_run3 (2)

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

unread,

[syzbot] [bpf?] [trace?] KASAN: slab-use-after-free Read in bpf_trace_run3 (2)

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

Feb 27

syzbot, … Qing Wang9

Feb 26

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

On Fri, 27 Feb 2026 at 00:52, Steven Rostedt <ros...@goodmis.org> wrote: > OK, so the issue

unread,

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

On Fri, 27 Feb 2026 at 00:52, Steven Rostedt <ros...@goodmis.org> wrote: > OK, so the issue

Feb 26

syzbot, … Hillf Danton28

Feb 26

[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

Feb 26

Feb 26

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

Hello, syzbot found the following issue on: HEAD commit: 189f164e573e Convert remaining multi-line

unread,

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

Hello, syzbot found the following issue on: HEAD commit: 189f164e573e Convert remaining multi-line

Feb 26

Feb 26

[syzbot] [rds?] possible deadlock in rds_tcp_tune (2)

> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git main This crash does not

unread,

[syzbot] [rds?] possible deadlock in rds_tcp_tune (2)

> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git main This crash does not

Feb 26

syzbot ci, Kuniyuki Iwashima2

Feb 26

[syzbot ci] Re: ipmr: No RTNL for RTNL_FAMILY_IPMR rtnetlink.

From: syzbot ci <syzbot+ci7bf...@syzkaller.appspotmail.com> Date: Thu, 26 Feb 2026 09

unread,

[syzbot ci] Re: ipmr: No RTNL for RTNL_FAMILY_IPMR rtnetlink.

From: syzbot ci <syzbot+ci7bf...@syzkaller.appspotmail.com> Date: Thu, 26 Feb 2026 09

Feb 26

syzbot ci, … syzbot ci8

Feb 26

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

Unknown command

unread,

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

Unknown command

Feb 26

Mauricio Faria de Oliveira, syzbot6

Feb 26

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

#syz dup: KASAN: slab-use-after-free Write in number

unread,

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

#syz dup: KASAN: slab-use-after-free Write in number

Feb 26

syzbot, Will Deacon2

Feb 26

[syzbot] [arm?] BUG: using __this_cpu_read() in preemptible code in __delay

On Thu, Feb 26, 2026 at 07:05:25AM -0800, syzbot wrote: > syzbot found the following issue on:

unread,

[syzbot] [arm?] BUG: using __this_cpu_read() in preemptible code in __delay

On Thu, Feb 26, 2026 at 07:05:25AM -0800, syzbot wrote: > syzbot found the following issue on:

Feb 26

Search

Clear search

Close search

Google apps

Main menu