From: Alasdair G Kergon <agk@redhat.com>
To: linux-lvm@redhat.com, linux-cluster@redhat.com
Subject: [linux-lvm] lvm2-cluster (clvmd) security fix (Moderate)
Date: Wed, 28 Jul 2010 17:41:12 +0100 [thread overview]
Message-ID: <20100728164112.GG15417@agk-dp.fab.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
I have released version 2.02.72 of LVM2 today to address a security problem.
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.72.tgz
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.72.tgz.asc
If you are running clvmd on a machine where you also have non-root users
you should seriously consider applying the patch, The problem has been
in the code base since 2004. LVM2 on its own is not vulnerable to this
problem.
Vendors were notified last week.
Red Hat's Security Advisories are here:
https://rhn.redhat.com/errata/RHSA-2010-0567.html
https://rhn.redhat.com/errata/RHSA-2010-0568.html
Fuller details are in the Red Hat Bugzilla:
https://bugzilla.redhat.com/CVE-2010-2526
The essential part of the patch is attached there and it should apply to
older releases too.
Alasdair
--
agk@redhat.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2010-07-28 16:41 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=20100728164112.GG15417@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-cluster@redhat.com \
--cc=linux-lvm@redhat.com \
/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).