All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix CVE-2007-1320, CVE-2007-1321 , CVE-2007-1322, CVE-2007-1323 and  CVE-2007-1366
Date: Tue, 1 May 2007 23:46:02 +0300	[thread overview]
Message-ID: <200705012346.05020.caglar@pardus.org.tr> (raw)
In-Reply-To: <C25D5DA6.6AE5%Keir.Fraser@cl.cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1824 bytes --]

01 May 2007 Sal tarihinde, Keir Fraser şunları yazmıştı: 
> On 1/5/07 19:56, "S.Çağlar Onur" <caglar@pardus.org.tr> wrote:
> > Hmm i think there are some :)
> >
> > I have following patches on top of current 3.0.5-testing tree, this
> > series contains all released CVE's from 2.6.18 to up until now (linus's
> > current git), only CVE-2007-2242 ( IPV6: Disallow RH0 by default.) is
> > missing...
>
> Presumably we'd get most of these by upgrading to linux-2.6.18.8?

8 of them are in 2.6.18.8 others are backported/applied etc,

CVE-2005-4352.patch <- solved with 2.6.18.3
CVE-2006-4814.patch <- solved with 2.6.18.8 
CVE-2006-5619.patch <- solved with 2.6.18.2
CVE-2006-5749.patch <- solved with 2.6.20-rc2
CVE-2006-5751.patch <- solved with 2.6.18.4
CVE-2006-5753.patch <- solved with 2.6.20-rc4
CVE-2006-5757-CVE-2006-6060.patch <- solved in 2.6.18.8
CVE-2006-5823.patch <- solved with 2.6.20-rc1
CVE-2006-6053.patch <- solved with 2.6.20-rc1
CVE-2006-6054.patch <- solved with 2.6.20-rc1
CVE-2006-6056.patch <- solved with 2.6.18.8 
CVE-2006-6106.patch <- solved with 2.6.18.6
CVE-2006-6333.patch <- solved with 2.6.20
CVE-2007-0005.patch <- solved with 2.6.21-rc3
CVE-2007-0006.patch <- solved with 2.6.21
CVE-2007-0772.patch <- solved with 2.6.18.7
CVE-2007-0958.patch <- solved with 2.6.20-rc7
CVE-2007-1000.patch <- solved with 2.6.21
CVE-2007-1217.patch <- solved with 2.6.20.1
CVE-2007-1388.patch <- solved with 2.6.21
CVE-2007-1497.patch <- solved with 2.6.21
CVE-2007-1592.patch <- solved with 2.6.21
CVE-2007-1861.patch <- solved with 2.6.21.1
CVE-2007-2172.patch <- solved with 2.6.20.6

Cheers
-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2007-05-01 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:29 [PATCH] Fix CVE-2007-1320, CVE-2007-1321 , CVE-2007-1322, CVE-2007-1323 and CVE-2007-1366 S.Çağlar Onur
2007-05-01 13:44 ` Keir Fraser
2007-05-01 14:15   ` S.Çağlar Onur
2007-05-01 14:44     ` Keir Fraser
2007-05-01 18:56       ` S.Çağlar Onur
2007-05-01 20:12         ` Keir Fraser
2007-05-01 20:46           ` S.Çağlar Onur [this message]
2007-05-01 23:04         ` S.Çağlar Onur
2007-05-01 18:14 ` Christian Limpach
2007-05-01 19:21   ` S.Çağlar Onur
2007-09-25 22:45   ` Robert Buchholz

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=200705012346.05020.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.