public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.37
Date: Mon, 8 Jan 2007 22:49:10 +0100	[thread overview]
Message-ID: <20070108214910.GD6167@stusta.de> (raw)
In-Reply-To: <200701070337_MC3-1-D79B-2928@compuserve.com>

On Sun, Jan 07, 2007 at 03:35:21AM -0500, Chuck Ebbert wrote:
> In-Reply-To: <20070104222517.GL20714@stusta.de>
> 
> On Thu, 4 Jan 2007 23:25:17 +0100, Adrian Bunk wrote:
> 
> > There's already a CVE number for
> > "i386: save/restore eflags in context switch".
> > 
> > Are there also CVE numbers for the equivalent x86_64 patch and
> > "x86_64: fix ia32 syscall count"?
> 
> Sorry, my Web access is broken for now so I can't check, but I believe
> that CVE number is for a different, older problem.
> 
> So AFAIK there are no CVE numbers for anything I sent (but there
> probably should be.)  Generic Linux kernel developers don't have
> a CVE representative, so we depend on vendors to assign numbers
> and sometimes they don't.

I asked on vendor-sec and got CVE-2006-5755 for the x86_64 equivalent of 
CVE-2006-5173, but none for the syscall count issue.

The latter is IMHO OK since "local user can spam syslog" is really 
borderline - there are simply too many DoS possibilities for local 
users.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-01-08 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07  8:35 Linux 2.6.16.37 Chuck Ebbert
2007-01-08 21:49 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-31 22:05 Chuck Ebbert
2007-01-04 22:25 ` Adrian Bunk
2006-12-28 13:53 Adrian Bunk

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=20070108214910.GD6167@stusta.de \
    --to=bunk@stusta.de \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@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