Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer

From: Jakub Kicinski
Date: Tue May 23 2023 - 12:46:13 EST

Next message: David Zheng: "[PATCH v1] i2c: designware: fix idx_write_cnt in read loop"
Previous message: Conor Dooley: "Re: [PATCH] dt-bindings: clock: qcom: Accept power-domains for GPUCC"
In reply to: Jason A. Donenfeld: "Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer"
Next in thread: Jason A. Donenfeld: "Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 23 May 2023 18:14:18 +0200 Jason A. Donenfeld wrote:
> So, IOW, not a wireguard bug, right?

What's slightly concerning is that there aren't any other timers
leading to

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

:( If WG was just an innocent bystander there should be, right?

Next message: David Zheng: "[PATCH v1] i2c: designware: fix idx_write_cnt in read loop"
Previous message: Conor Dooley: "Re: [PATCH] dt-bindings: clock: qcom: Accept power-domains for GPUCC"
In reply to: Jason A. Donenfeld: "Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer"
Next in thread: Jason A. Donenfeld: "Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]