[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210610164352.GQ20020@breakpoint.cc>
Date: Thu, 10 Jun 2021 18:43:52 +0200
From: Florian Westphal <fw@...len.de>
To: Maxim Mikityanskiy <maximmi@...dia.com>
Cc: Mat Martineau <mathew.j.martineau@...ux.intel.com>,
Matthieu Baerts <matthieu.baerts@...sares.net>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Florian Westphal <fw@...len.de>,
Toke Høiland-Jørgensen <toke@...e.dk>,
Jamal Hadi Salim <jhs@...atatu.com>,
Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
Patrick McHardy <kaber@...sh.net>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Paolo Abeni <pabeni@...hat.com>,
Christoph Paasch <cpaasch@...le.com>,
Peter Krystad <peter.krystad@...ux.intel.com>,
Young Xiao <92siuyang@...il.com>, netdev@...r.kernel.org,
mptcp@...ts.linux.dev
Subject: Re: [PATCH net v2 1/3] netfilter: synproxy: Fix out of bounds when
parsing TCP options
Maxim Mikityanskiy <maximmi@...dia.com> wrote:
> The TCP option parser in synproxy (synproxy_parse_options) could read
> one byte out of bounds. When the length is 1, the execution flow gets
> into the loop, reads one byte of the opcode, and if the opcode is
> neither TCPOPT_EOL nor TCPOPT_NOP, it reads one more byte, which exceeds
> the length of 1.
>
> This fix is inspired by commit 9609dad263f8 ("ipv4: tcp_input: fix stack
> out of bounds when parsing TCP options.").
Reviewed-by: Florian Westphal <fw@...len.de>
Powered by blists - more mailing lists