From: Greg KH <greg@kroah.com>
To: Ajay Kaher <akaher@vmware.com>
Cc: stable@vger.kernel.org, pablo@netfilter.org,
kadlec@netfilter.org, fw@strlen.de, davem@davemloft.net,
netfilter-devel@vger.kernel.org, srivatsab@vmware.com,
srivatsa@csail.mit.edu, amakhalov@vmware.com, anishs@vmware.com,
vsirnapalli@vmware.com, er.ajay.kaher@gmail.com
Subject: Re: [PATCH v5.4.y] netfilter: nf_tables: disallow non-stateful expression in sets earlier
Date: Mon, 6 Jun 2022 14:08:49 +0200 [thread overview]
Message-ID: <Yp3uURb8M7XWFw3E@kroah.com> (raw)
In-Reply-To: <1654503264-47182-1-git-send-email-akaher@vmware.com>
On Mon, Jun 06, 2022 at 01:44:24PM +0530, Ajay Kaher wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.org>
>
> commit 520778042ccca019f3ffa136dd0ca565c486cedd upstream.
>
> Since 3e135cd499bf ("netfilter: nft_dynset: dynamic stateful expression
> instantiation"), it is possible to attach stateful expressions to set
> elements.
>
> cd5125d8f518 ("netfilter: nf_tables: split set destruction in deactivate
> and destroy phase") introduces conditional destruction on the object to
> accomodate transaction semantics.
>
> nft_expr_init() calls expr->ops->init() first, then check for
> NFT_STATEFUL_EXPR, this stills allows to initialize a non-stateful
> lookup expressions which points to a set, which might lead to UAF since
> the set is not properly detached from the set->binding for this case.
> Anyway, this combination is non-sense from nf_tables perspective.
>
> This patch fixes this problem by checking for NFT_STATEFUL_EXPR before
> expr->ops->init() is called.
>
> The reporter provides a KASAN splat and a poc reproducer (similar to
> those autogenerated by syzbot to report use-after-free errors). It is
> unknown to me if they are using syzbot or if they use similar automated
> tool to locate the bug that they are reporting.
>
> For the record, this is the KASAN splat.
>
> [ 85.431824] ==================================================================
> [ 85.432901] BUG: KASAN: use-after-free in nf_tables_bind_set+0x81b/0xa20
> [ 85.433825] Write of size 8 at addr ffff8880286f0e98 by task poc/776
> [ 85.434756]
> [ 85.434999] CPU: 1 PID: 776 Comm: poc Tainted: G W 5.18.0+ #2
> [ 85.436023] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
>
> Fixes: 0b2d8a7b638b ("netfilter: nf_tables: add helper functions for expression handling")
> Reported-and-tested-by: Aaron Adams <edg-e@nccgroup.com>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> [Ajay: Regenerated the patch for v5.4.y]
> Signed-off-by: Ajay Kaher <akaher@vmware.com>
> ---
> net/netfilter/nf_tables_api.c | 16 ++++++++++------
> net/netfilter/nft_dynset.c | 3 ---
> 2 files changed, 10 insertions(+), 9 deletions(-)
Both backports now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-06 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 8:14 [PATCH v5.4.y] netfilter: nf_tables: disallow non-stateful expression in sets earlier Ajay Kaher
2022-06-06 12:08 ` Greg KH [this message]
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=Yp3uURb8M7XWFw3E@kroah.com \
--to=greg@kroah.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=davem@davemloft.net \
--cc=er.ajay.kaher@gmail.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=vsirnapalli@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).