syzkaller-bugs - Google Groups

Groups

Contact owners and managers

1–30 of 18454

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:08 AM

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

Hello, syzbot found the following issue on: HEAD commit: cf72cbb39da8 Merge tag 'io_uring-7.3-

unread,

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

Hello, syzbot found the following issue on: HEAD commit: cf72cbb39da8 Merge tag 'io_uring-7.3-

5:08 AM

syzbot, Yu, Tao17

4:24 AM

[syzbot] [edac?] general protection fault in detach_timer (3)

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

unread,

[syzbot] [edac?] general protection fault in detach_timer (3)

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

4:24 AM

syzbot, … Junjie Cao10

4:22 AM

[syzbot] [mm?] INFO: rcu detected stall in exit_to_user_mode_loop

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

unread,

[syzbot] [mm?] INFO: rcu detected stall in exit_to_user_mode_loop

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

4:22 AM

syzbot, … Junjie Cao16

3:55 AM

[syzbot] [mm?] INFO: rcu detected stall in sys_munmap (2)

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

unread,

[syzbot] [mm?] INFO: rcu detected stall in sys_munmap (2)

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

3:55 AM

syzbot, Junjie Cao6

3:45 AM

[syzbot] [kernfs?] [mm?] INFO: rcu detected stall in kernfs_fop_open (7)

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

unread,

[syzbot] [kernfs?] [mm?] INFO: rcu detected stall in kernfs_fop_open (7)

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

3:45 AM

syzbot, … Hillf Danton3

3:34 AM

[syzbot] [kvm?] INFO: task hung in kvm_gmem_release

On Mon, 31 Aug 2026 08:15:44 -0700 Sean Christopherson wrote: >On Mon, Aug 31, 2026, syzbot wrote:

unread,

[syzbot] [kvm?] INFO: task hung in kvm_gmem_release

On Mon, 31 Aug 2026 08:15:44 -0700 Sean Christopherson wrote: >On Mon, Aug 31, 2026, syzbot wrote:

3:34 AM

3:05 AM

[PATCH] can: j1939: fix memory leaks caused by pending address claim timer

From: Slawomir Stepien <s...@poczta.fm> A memory leak of struct j1939_ecu and struct j1939_priv

unread,

[PATCH] can: j1939: fix memory leaks caused by pending address claim timer

From: Slawomir Stepien <s...@poczta.fm> A memory leak of struct j1939_ecu and struct j1939_priv

3:05 AM

2:59 AM

[syzbot ci] Re: block: brd/loop error-path cleanup

syzbot ci has tested the following series [v1] block: brd/loop error-path cleanup https://lore.kernel

unread,

[syzbot ci] Re: block: brd/loop error-path cleanup

syzbot ci has tested the following series [v1] block: brd/loop error-path cleanup https://lore.kernel

2:59 AM

syzbot, xietangxin2

2:57 AM

[syzbot] [sctp?] WARNING: refcount bug in sctp_transport_put (6)

Hi, I have analyzed this issue and successfully reproduced locally. The race occurs between the timer

unread,

[syzbot] [sctp?] WARNING: refcount bug in sctp_transport_put (6)

Hi, I have analyzed this issue and successfully reproduced locally. The race occurs between the timer

2:57 AM

syzbot, Hillf Danton3

2:55 AM

[syzbot] [i2c?] [usb?] INFO: task hung in em28xx_i2c_unregister

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

unread,

[syzbot] [i2c?] [usb?] INFO: task hung in em28xx_i2c_unregister

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

2:55 AM

Aug 31

[syzbot] [ext4?] general protection fault in __bh_submit

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

unread,

[syzbot] [ext4?] general protection fault in __bh_submit

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

Aug 31

Aug 31

[syzbot] WARNING in cfg80211_pernet_exit

Hello, syzbot found the following issue on: HEAD commit: 73ae59e97596 Merge tag 'erofs-for-7.3-

unread,

[syzbot] WARNING in cfg80211_pernet_exit

Hello, syzbot found the following issue on: HEAD commit: 73ae59e97596 Merge tag 'erofs-for-7.3-

Aug 31

David Woodhouse3

Aug 31

[PATCH v3 0/13] KVM: x86/xen: Bug fixes and long_mode cleanup

From: David Woodhouse <dw...@amazon.co.uk> Rename in preparation for adding a variant that takes

unread,

[PATCH v3 0/13] KVM: x86/xen: Bug fixes and long_mode cleanup

From: David Woodhouse <dw...@amazon.co.uk> Rename in preparation for adding a variant that takes

Aug 31

David Woodhouse

Aug 31

[PATCH v3 13/13] KVM: x86/xen: Convert evtchn_ports from IDR to XArray

From: Furkan Caliskan <frn1fu...@gmail.com> IDR is deprecated in favor of XArray: see

unread,

[PATCH v3 13/13] KVM: x86/xen: Convert evtchn_ports from IDR to XArray

From: Furkan Caliskan <frn1fu...@gmail.com> IDR is deprecated in favor of XArray: see

Aug 31

David Woodhouse

Aug 31

[PATCH v3 05/13] KVM: x86/xen: Latch shinfo mode in kvm_xen_schedop_poll()

From: David Woodhouse <dw...@amazon.co.uk> kvm_xen_schedop_poll() validates port numbers against

unread,

[PATCH v3 05/13] KVM: x86/xen: Latch shinfo mode in kvm_xen_schedop_poll()

From: David Woodhouse <dw...@amazon.co.uk> kvm_xen_schedop_poll() validates port numbers against

Aug 31

David Woodhouse

Aug 31

[PATCH v3 01/13] KVM: x86/xen: Rename 'longmode' to 'is_64bit' in hypercall handling

From: David Woodhouse <dw...@amazon.co.uk> Rename the local 'longmode' variable and

unread,

[PATCH v3 01/13] KVM: x86/xen: Rename 'longmode' to 'is_64bit' in hypercall handling

From: David Woodhouse <dw...@amazon.co.uk> Rename the local 'longmode' variable and

Aug 31

David Woodhouse

Aug 31

[PATCH v3 10/13] KVM: x86/xen: Take kvm->srcu in __kvm_xen_has_interrupt()

From: David Woodhouse <dw...@amazon.co.uk> kvm_gpc_check() checks the cached memslot generation

unread,

[PATCH v3 10/13] KVM: x86/xen: Take kvm->srcu in __kvm_xen_has_interrupt()

From: David Woodhouse <dw...@amazon.co.uk> kvm_gpc_check() checks the cached memslot generation

Aug 31

David Woodhouse

Aug 31

[PATCH v3 04/13] KVM: x86/xen: Latch shinfo mode in kvm_xen_set_evtchn_fast()

From: Hyunwoo Kim <imv...@gmail.com> kvm_xen_set_evtchn_fast() assumes the port range check in

unread,

[PATCH v3 04/13] KVM: x86/xen: Latch shinfo mode in kvm_xen_set_evtchn_fast()

From: Hyunwoo Kim <imv...@gmail.com> kvm_xen_set_evtchn_fast() assumes the port range check in

Aug 31

David Woodhouse

Aug 31

[PATCH v3 09/13] KVM: x86/xen: Use atomic*() APIs instead of open coded equivalents

From: Sean Christopherson <sea...@google.com> Replace the open coded atomic asm blobs in the

unread,

[PATCH v3 09/13] KVM: x86/xen: Use atomic*() APIs instead of open coded equivalents

From: Sean Christopherson <sea...@google.com> Replace the open coded atomic asm blobs in the

Aug 31

David Woodhouse

Aug 31

[PATCH v3 12/13] KVM: pfncache: use a dedicated invalidation sequence for cache refresh

From: David Woodhouse <dw...@amazon.co.uk> The gfn_to_pfn_cache refresh path guards against mmu

unread,

[PATCH v3 12/13] KVM: pfncache: use a dedicated invalidation sequence for cache refresh

From: David Woodhouse <dw...@amazon.co.uk> The gfn_to_pfn_cache refresh path guards against mmu

Aug 31

David Woodhouse

Aug 31

[PATCH v3 02/13] KVM: x86/xen: Introduce kvm_xen_has_64bit_shinfo() macro

From: David Woodhouse <dw...@amazon.co.uk> Add a kvm_xen_has_64bit_shinfo() helper macro to

unread,

[PATCH v3 02/13] KVM: x86/xen: Introduce kvm_xen_has_64bit_shinfo() macro

From: David Woodhouse <dw...@amazon.co.uk> Add a kvm_xen_has_64bit_shinfo() helper macro to

Aug 31

David Woodhouse

Aug 31

[PATCH v3 11/13] KVM: x86/xen: Mark poll_evtchn accesses with READ_ONCE()/WRITE_ONCE()

From: Chengfeng Ye <nicoy...@gmail.com> Use READ_ONCE() and WRITE_ONCE() for runtime

unread,

[PATCH v3 11/13] KVM: x86/xen: Mark poll_evtchn accesses with READ_ONCE()/WRITE_ONCE()

From: Chengfeng Ye <nicoy...@gmail.com> Use READ_ONCE() and WRITE_ONCE() for runtime

Aug 31

David Woodhouse

Aug 31

[PATCH v3 07/13] KVM: x86/xen: Use 32-bit locked bts for vcpu_info evtchn_pending_sel

From: David Woodhouse <dw...@amazon.co.uk> Replace test_and_set_bit() on vcpu_info->

unread,

[PATCH v3 07/13] KVM: x86/xen: Use 32-bit locked bts for vcpu_info evtchn_pending_sel

From: David Woodhouse <dw...@amazon.co.uk> Replace test_and_set_bit() on vcpu_info->

Aug 31

David Woodhouse

Aug 31

[PATCH v3 06/13] KVM: x86/xen: Enforce 4-byte alignment of vcpu_info registration

From: David Woodhouse <dw...@amazon.co.uk> Xen's map_guest_area() enforces that vcpu_info is

unread,

[PATCH v3 06/13] KVM: x86/xen: Enforce 4-byte alignment of vcpu_info registration

From: David Woodhouse <dw...@amazon.co.uk> Xen's map_guest_area() enforces that vcpu_info is

Aug 31

syzbot, … Bart Van Assche4

Aug 31

[syzbot] [block?] BUG: corrupted list in blk_mq_request_bypass_insert

On 8/31/26 7:58 AM, Keith Busch wrote: > We want to be able to retry eligible commands that were

unread,

[syzbot] [block?] BUG: corrupted list in blk_mq_request_bypass_insert

On 8/31/26 7:58 AM, Keith Busch wrote: > We want to be able to retry eligible commands that were

Aug 31

syzbot, … Shakeel Butt9

Aug 31

[syzbot] [mm?] WARNING in __mod_zone_page_state

On Sun, Aug 30, 2026 at 10:29:46AM -0700, Hugh Dickins wrote: > On Sat, 29 Aug 2026, Shakeel Butt

unread,

[syzbot] [mm?] WARNING in __mod_zone_page_state

On Sun, Aug 30, 2026 at 10:29:46AM -0700, Hugh Dickins wrote: > On Sat, 29 Aug 2026, Shakeel Butt

Aug 31

Aug 31

[syzbot] [fs?] KASAN: slab-use-after-free Read in sysfs_emit

syzbot has found a reproducer for the following issue on: HEAD commit: f1b8fa82cab7 Merge branch

unread,

[syzbot] [fs?] KASAN: slab-use-after-free Read in sysfs_emit

syzbot has found a reproducer for the following issue on: HEAD commit: f1b8fa82cab7 Merge branch

Aug 31

syzbot, patchwork-b...@kernel.org2

Aug 31

[PATCH] Bluetooth: hci_core: Fix race condition during device registration

Hello: This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <

unread,

[PATCH] Bluetooth: hci_core: Fix race condition during device registration

Hello: This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <

Aug 31

syzbot, Takashi Iwai3

Aug 31

[syzbot] [kernel?] BUG: scheduling while atomic in drain_urb_queue

On Fri, 28 Aug 2026 18:17:32 +0200, syzbot wrote: > > syzbot has found a reproducer for the

unread,

[syzbot] [kernel?] BUG: scheduling while atomic in drain_urb_queue

On Fri, 28 Aug 2026 18:17:32 +0200, syzbot wrote: > > syzbot has found a reproducer for the

Aug 31

Aug 31

[syzbot] [kernel?] INFO: rcu detected stall in __hrtimer_run_queues (3)

syzbot has found a reproducer for the following issue on: HEAD commit: f1b8fa82cab7 Merge branch

unread,

[syzbot] [kernel?] INFO: rcu detected stall in __hrtimer_run_queues (3)

syzbot has found a reproducer for the following issue on: HEAD commit: f1b8fa82cab7 Merge branch

Aug 31

Search

Clear search

Close search

Google apps

Main menu