From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] util-linux: security bump to version 2.29.2
Date: Thu, 23 Feb 2017 12:42:54 -0300 (BRT) [thread overview]
Message-ID: <595202195.11970979.1487864574446.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20170223085742.C646982235@busybox.osuosl.org>
> From: "Peter Korsgaard" <peter@korsgaard.com>
> To: buildroot at buildroot.org
> Sent: Thursday, February 23, 2017 5:55:57 AM
> Subject: [Buildroot] [git commit] util-linux: security bump to version 2.29.2
> commit:
> https://git.buildroot.net/buildroot/commit/?id=a5015f1025a1aee173c2c2ab39ccac5ce38f30c3
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> From
> https://www.kernel.org/pub/linux/utils/util-linux/v2.29/v2.29.2-ReleaseNotes
>
> This release fixes su(1) security issue CVE-2017-2616:
>
> It is possible for any local user to send SIGKILL to other processes with root
> privileges. To exploit this, the user must be able to perform su with a
> successful login. SIGKILL can only be sent to processes which were executed
> after the su process. It is not possible to send SIGKILL to processes which
> were already running.
Should not this go to next too, since it is a security fix?
--
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent
success of having your words and actions judged by your reputation,
rather than the other way about.? ? Christopher Hitchens
next prev parent reply other threads:[~2017-02-23 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 8:55 [Buildroot] [git commit] util-linux: security bump to version 2.29.2 Peter Korsgaard
2017-02-23 15:42 ` Carlos Santos [this message]
2017-02-23 20:34 ` Peter Korsgaard
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=595202195.11970979.1487864574446.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=buildroot@busybox.net \
/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.