From: Greg KH <greg@kroah.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Saleem Abdulrasool <compnerd@compnerd.org>,
"John W.Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, chrisw@sous-sol.org,
stable@kernel.org
Subject: Re: [PATCH] iwlwifi: fix possible NULL dereference in iwl_set_rate()
Date: Mon, 19 Nov 2007 11:10:09 -0800 [thread overview]
Message-ID: <20071119191009.GB9115@kroah.com> (raw)
In-Reply-To: <1195460046.3250.380.camel@debian.sh.intel.com>
On Mon, Nov 19, 2007 at 04:14:06PM +0800, Zhu Yi wrote:
> On Sun, 2007-11-18 at 23:59 -0800, Saleem Abdulrasool wrote:
> > As per Zhu Yi's request, Im forwarding along a patch for CVE-2007-5938, a NULL
> > dereference vulnerability in the iwlwifi driver. All current versions are
> > effected by this.
>
> ACK.
Please let the stable@kernel.org address know when this patch goes into
Linus's tree, so that we can apply it there.
thanks,
greg k-h
prev parent reply other threads:[~2007-11-19 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 7:59 [PATCH] iwlwifi: fix possible NULL dereference in iwl_set_rate() Saleem Abdulrasool
2007-11-19 8:14 ` Zhu Yi
2007-11-19 19:10 ` Greg KH [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=20071119191009.GB9115@kroah.com \
--to=greg@kroah.com \
--cc=chrisw@sous-sol.org \
--cc=compnerd@compnerd.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@kernel.org \
--cc=yi.zhu@intel.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).