From: Willy Tarreau <w@1wt.eu>
To: dann frazier <dannf@hp.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] 2.4: [SCSI] aacraid: Fix security hole
Date: Tue, 5 Feb 2008 20:31:56 +0100 [thread overview]
Message-ID: <20080205193155.GA25898@1wt.eu> (raw)
In-Reply-To: <20080205103327.GB1792@ldl.fc.hp.com>
Hi Dann,
On Tue, Feb 05, 2008 at 03:33:28AM -0700, dann frazier wrote:
> This is a 2.4 backport of a linux-2.6 change by Alan Cox.
> (commit 60395bb60e0b5e4e0808ac8eb07a92f6c9cdea1f)
>
> It has been build-tested only (I don't have the hardware).
> CVE-2007-4308 was assigned for this issue.
>
> Commit log from 2.6 follows.
>
> On the SCSI layer ioctl path there is no implicit permissions check for
> ioctls (and indeed other drivers implement unprivileged ioctls). aacraid
> however allows all sorts of very admin only things to be done so should
> check.
OK, makes sense. I did not notice that one in 2.6, eventhough Alan clearly
stated a security hole in the subject.
I'm applying it now, thanks!
Willy
prev parent reply other threads:[~2008-02-05 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 10:33 [PATCH] 2.4: [SCSI] aacraid: Fix security hole dann frazier
2008-02-05 19:31 ` Willy Tarreau [this message]
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=20080205193155.GA25898@1wt.eu \
--to=w@1wt.eu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dannf@hp.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