lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CADVnQyn8Mr6FjZjaxPE=9H0GcnThfZX_DHWoM+TwMczPNKpjCg@mail.gmail.com> Date: Wed, 31 Aug 2022 08:55:49 -0400 From: Neal Cardwell <ncardwell@...gle.com> To: Eric Dumazet <eric.dumazet@...il.com> Cc: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, netdev <netdev@...r.kernel.org>, Jason Baron <jbaron@...mai.com>, Eric Dumazet <edumazet@...gle.com>, syzbot <syzkaller@...glegroups.com> Subject: Re: [PATCH net 1/2] tcp: annotate data-race around challenge_timestamp On Tue, Aug 30, 2022 at 2:57 PM Eric Dumazet <eric.dumazet@...il.com> wrote: > > From: Eric Dumazet <edumazet@...gle.com> > > challenge_timestamp can be read an written by concurrent threads. > > This was expected, but we need to annotate the race to avoid potential issues. > > Following patch moves challenge_timestamp and challenge_count > to per-netns storage to provide better isolation. > > Fixes: 354e4aa391ed ("tcp: RFC 5961 5.2 Blind Data Injection Attack Mitigation") > Reported-by: syzbot <syzkaller@...glegroups.com> > Signed-off-by: Eric Dumazet <edumazet@...gle.com> > --- Acked-by: Neal Cardwell <ncardwell@...gle.com> Thanks, Eric! neal
Powered by blists - more mailing lists