From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE] LTTng-modules 2.9.6 and 2.10.3 (Linux kernel tracer)
Date: Fri, 3 Nov 2017 21:33:11 +0000 (UTC) [thread overview]
Message-ID: <2109876270.3592.1509744791959.JavaMail.zimbra@efficios.com> (raw)
Hi,
Versions 2.9.6 and 2.10.3 fix an input validation issue with
the /proc/lttng-logger interface of lttng-modules. An ill-crafted input
to the write system call to /proc/lttng-logger can trigger a kernel OOPS.
Given that all users can write to that file, it means that arbitrary
local users can trigger a kernel OOPS. It would be preferable to
upgrade your lttng-modules to a version containing this fix.
Thanks,
Mathieu
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Changelog:
2017-11-03 (National Sandwich Day) LTTng modules 2.9.6
* Fix: lttng-logger get_user_pages_fast error handling
2017-11-03 (National Sandwich Day) LTTng modules 2.10.3
* Fix: lttng-logger get_user_pages_fast error handling
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2017-11-03 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2109876270.3592.1509744791959.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=lttng-dev@lists.lttng.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