From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Status of KVM vulnerabilities
Date: Thu, 11 Mar 2010 06:52:52 -0300 [thread overview]
Message-ID: <20100311095252.GA29115@defiant.freesoftware> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hi, all.
Recently Debian has published the DSA-2010-1 [1] where the following
vulnerabilities are fixed:
* CVE-2010-0298 & CVE-2010-0306 (Gleb Natapov)
* CVE-2010-0309 (Marcelo Tosatti)
* CVE-2010-0419 (Paolo Bonzini)
I'm using Linux 2.6.32.3 with qemu-kvm-0.12.1.2 and I would like to know
if it is necessary to update kvm-kmod or qemu-kvm, if some of these
versions presents this vulnerability and some new version already exists
and fix it.
Thanks in advance for your replies.
Regards,
Daniel
[1] http://seclists.org/bugtraq/2010/Mar/98
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2010-03-11 9:52 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=20100311095252.GA29115@defiant.freesoftware \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--cc=kvm@vger.kernel.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