From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mbuffer: fix use-after-free.
Date: Mon, 15 Mar 2021 20:36:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29494@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
There is a new pull request by ericonr against master on the void-packages repository
https://github.com/ericonr/void-packages mbu
https://github.com/void-linux/void-packages/pull/29494
mbuffer: fix use-after-free.
Fixes segfault on musl when killed with SIGINT.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/29494.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mbu-29494.patch --]
[-- Type: text/x-diff, Size: 2532 bytes --]
From d22893ffbad14b6cbf081b87a46578b667f4d329 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Nogueira?= <erico.erc@gmail.com>
Date: Mon, 15 Mar 2021 16:35:11 -0300
Subject: [PATCH] mbuffer: fix use-after-free.
Fixes segfault on musl when killed with SIGINT.
---
.../0001-mbuffer-don-t-cancel-ReaderThr.patch | 33 +++++++++++++++++++
srcpkgs/mbuffer/template | 3 +-
2 files changed, 35 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/mbuffer/patches/0001-mbuffer-don-t-cancel-ReaderThr.patch
diff --git a/srcpkgs/mbuffer/patches/0001-mbuffer-don-t-cancel-ReaderThr.patch b/srcpkgs/mbuffer/patches/0001-mbuffer-don-t-cancel-ReaderThr.patch
new file mode 100644
index 000000000000..1dd160547225
--- /dev/null
+++ b/srcpkgs/mbuffer/patches/0001-mbuffer-don-t-cancel-ReaderThr.patch
@@ -0,0 +1,33 @@
+Subject: [PATCH] mbuffer: don't cancel ReaderThr.
+
+joinSenders is called after ReaderThr has been joined, which makes the
+pthread_cancel call in cancelAll undefined behavior and a case of
+use-after-free. Since the thread will already have been joined in main
+by the time joinSenders is called, there is no need to cancel it, so
+that call can simply be removed.
+
+Furthermore, we don't have to account for situations where pthread_join
+can fail, because this program doesn't generate them. If there were
+other threads which tried to join readerThr at the same time, a
+successful pthread_join call should also set Status=0, so pthread_cancel
+isn't called. However, that isn't necessary.
+---
+ mbuffer.c | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/mbuffer.c b/mbuffer.c
+index 79c997f..6e65277 100644
+--- a/mbuffer.c
++++ b/mbuffer.c
+@@ -166,8 +166,6 @@ static void cancelAll(void)
+ d->result = "canceled";
+ d = d->next;
+ } while (d);
+- if (Status)
+- (void) pthread_cancel(ReaderThr);
+ }
+
+
+--
+2.30.2
+
diff --git a/srcpkgs/mbuffer/template b/srcpkgs/mbuffer/template
index d3833b914ca4..fa30e2134c17 100644
--- a/srcpkgs/mbuffer/template
+++ b/srcpkgs/mbuffer/template
@@ -1,7 +1,7 @@
# Template file for 'mbuffer'
pkgname=mbuffer
version=20210209
-revision=1
+revision=2
build_style=gnu-configure
makedepends="openssl-devel"
checkdepends="tar"
@@ -11,4 +11,5 @@ license="GPL-3.0-or-later"
homepage="https://www.maier-komor.de/mbuffer.html"
distfiles="https://www.maier-komor.de/software/mbuffer/mbuffer-${version}.tgz"
checksum=e81f2788e2621f20f848181ef2cb19ac6d12328691437f301574b253fd899a0c
+patch_args=-Np1
conf_files="/etc/mbuffer.rc"
next reply other threads:[~2021-03-15 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:36 ericonr [this message]
2021-03-16 1:56 ` [PR PATCH] [Merged]: " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29494@inbox.vuxu.org \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 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).