From: Marcel Holtmann <marcel@holtmann.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, stable@kernel.org
Subject: Re: Linux 2.6.17.6
Date: Sun, 16 Jul 2006 02:18:03 +0200 [thread overview]
Message-ID: <1153009083.12764.18.camel@localhost> (raw)
In-Reply-To: <20060715193552.GA5330@kroah.com>
Hi Greg,
> This should fix the reported issue of NetworkManager dying when using
> the 2.6.17.5 kernel release. All users of the 2.6.17 kernel are
> recommended to upgrade to this kernel, as it fixes a publicly known
> security issue that can provide root access to any local user of the
> machine.
attached is the backported "don't allow chmod()" patch. Please consider
including it into the next stable release. Since the 2.6.17.6 kernel is
no longer vulnerable against CVE-2006-3626, this has no real urgent need
to get out.
Regards
Marcel
next prev parent reply other threads:[~2006-07-16 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 19:35 Linux 2.6.17.6 Greg KH
2006-07-15 19:36 ` Greg KH
2006-07-16 0:18 ` Marcel Holtmann [this message]
2006-07-16 0:20 ` Marcel Holtmann
2006-08-03 7:19 ` [stable] " Greg KH
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=1153009083.12764.18.camel@localhost \
--to=marcel@holtmann.org \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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