All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net] netfilter: xt_TCPMSS: add more sanity tests on tcph->doff
Date: Sat, 8 Apr 2017 22:24:43 +0200	[thread overview]
Message-ID: <20170408202443.GA3373@salvia> (raw)
In-Reply-To: <1491242111.10124.32.camel@edumazet-glaptop3.roam.corp.google.com>

On Mon, Apr 03, 2017 at 10:55:11AM -0700, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> Denys provided an awesome KASAN report pointing to an use
> after free in xt_TCPMSS
> 
> I have provided three patches to fix this issue, either in xt_TCPMSS or
> in xt_tcpudp.c. It seems xt_TCPMSS patch has the smallest possible
> impact.

Applied to nf.git, thanks!

  reply	other threads:[~2017-04-08 20:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02  7:43 KASAN, xt_TCPMSS finally found nasty use-after-free bug? 4.10.8 Denys Fedoryshchenko
2017-04-02 11:24 ` Eric Dumazet
2017-04-02 11:45   ` Florian Westphal
2017-04-02 11:51     ` Denys Fedoryshchenko
2017-04-02 11:54     ` Eric Dumazet
2017-04-02 12:19       ` Eric Dumazet
2017-04-02 12:25         ` Denys Fedoryshchenko
2017-04-02 12:32           ` Eric Dumazet
2017-04-02 16:52             ` Denys Fedoryshchenko
2017-04-02 17:14               ` Eric Dumazet
2017-04-02 17:26                 ` Eric Dumazet
2017-04-03  8:10                   ` Denys Fedoryshchenko
2017-04-03 12:09                     ` Eric Dumazet
2017-04-03 12:14                       ` Denys Fedoryshchenko
2017-04-03 12:24                         ` Eric Dumazet
2017-04-03 17:55   ` [PATCH net] netfilter: xt_TCPMSS: add more sanity tests on tcph->doff Eric Dumazet
2017-04-08 20:24     ` Pablo Neira Ayuso [this message]
2017-04-20 18:14       ` Denys Fedoryshchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170408202443.GA3373@salvia \
    --to=pablo@netfilter.org \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=nuclearcat@nuclearcat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.