From: Martin Doucha <mdoucha@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] Fix use after stack unwind in fzsync lib
Date: Fri, 27 Mar 2020 09:42:44 +0100 [thread overview]
Message-ID: <5b99cab2-5f9e-47f0-15f1-3dfdb02920ac@suse.cz> (raw)
In-Reply-To: <20200326204107.GA26499@dell5510>
On 26. 03. 20 21:41, Petr Vorel wrote:
> Hi Martin,
>
>> tst_fzsync_pair_reset() passes a local variable to thread B which may be
>> already unwinded by the time the thread wrapper function executes. If new
>> variables get allocated and initialized on stack between pthread_create()
>> and thread wrapper execution, thread B will segfault.
>
> I naively assumed this would fix SIGKILL signal for CVE 2018-1000199 test,
> but it didn't.
No, the fuzzysync fix is unrelated to the CVE-2018-1000199 test. I ran
into mysterious segfaults while writing a test for CVE-2018-18559 which
I haven't finished yet.
--
Martin Doucha mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic
prev parent reply other threads:[~2020-03-27 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:28 [LTP] [PATCH v3] Fix use after stack unwind in fzsync lib Martin Doucha
2020-03-26 15:43 ` Cyril Hrubis
2020-03-26 20:41 ` Petr Vorel
2020-03-27 8:42 ` Martin Doucha [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=5b99cab2-5f9e-47f0-15f1-3dfdb02920ac@suse.cz \
--to=mdoucha@suse.cz \
--cc=ltp@lists.linux.it \
/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.