From: Florian Westphal <fw@strlen.de>
To: Kyuwon Shim <Kyuwon.Shim@alliedtelesis.co.nz>
Cc: "fw@strlen.de" <fw@strlen.de>,
"pablo@netfilter.org" <pablo@netfilter.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v2] ulogd2: Avoid use after free in unregister on global ulogd_fds linked list
Date: Mon, 20 Mar 2023 23:10:22 +0100 [thread overview]
Message-ID: <20230320221022.GA4659@breakpoint.cc> (raw)
In-Reply-To: <7ee33839d49fe210dfb7347ea25724e9f43046e0.camel@alliedtelesis.co.nz>
Kyuwon Shim <Kyuwon.Shim@alliedtelesis.co.nz> wrote:
> Hi, Florian
> This is valgrind logs.
>
> ==4797== Memcheck, a memory error detector
> ==4797== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et
> al.
> ==4797== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright
> info
> ==4797== Command: ulogd -v -c /etc/ulogd.conf
> ==4797== Invalid read of size 4
> ==4797== at 0x405F60: ulogd_unregister_fd (select.c:74)
> ==4797== by 0x4E4E3DF: ??? (in /usr/lib/ulogd/ulogd_inppkt_NFLOG.so)
> ==4797== by 0x405003: stop_pluginstances (ulogd.c:1335)
> ==4797== by 0x405003: sigterm_handler_task (ulogd.c:1383)
> ==4797== by 0x405153: call_signal_handler_tasks (ulogd.c:424)
> ==4797== by 0x405153: signal_channel_callback (ulogd.c:443)
> ==4797== by 0x406163: ulogd_select_main (select.c:105)
> ==4797== by 0x403CF3: ulogd_main_loop (ulogd.c:1070)
> ==4797== by 0x403CF3: main (ulogd.c:1649)
> ==4797== Address 0x4a84f40 is 160 bytes inside a block of size 4,848
> free'd
Yuck, thanks for the backtrace. I've applied the patch with an amended
changelog and a comment wrt. ::stop doing such things.
next prev parent reply other threads:[~2023-03-20 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1678233154187.35009@alliedtelesis.co.nz>
2023-03-09 1:24 ` [PATCH v2] ulogd2: Avoid use after free in unregister on global ulogd_fds linked list Kyuwon Shim
2023-03-16 11:28 ` Florian Westphal
2023-03-20 20:41 ` Kyuwon Shim
2023-03-20 21:43 ` Jeremy Sowden
2023-03-20 22:10 ` Florian Westphal [this message]
2023-03-20 23:35 ` Kyuwon Shim
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=20230320221022.GA4659@breakpoint.cc \
--to=fw@strlen.de \
--cc=Kyuwon.Shim@alliedtelesis.co.nz \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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.