From: Eugene Teo <eugene@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: sfrench@us.ibm.com, chrisw@sous-sol.org, shirishp@us.ibm.com,
stable@kernel.org, vinaysridhar@in.ibm.com,
stable-commits@vger.kernel.org,
Jeffrey Layton <jlayton@redhat.com>
Subject: Re: patch 0022-CIFS-Fix-memory-overwrite-when-saving-nativeFileSys.patch added to 2.6.27-stable tree
Date: Mon, 20 Apr 2009 13:23:29 +0800 [thread overview]
Message-ID: <49EC06D1.7030208@redhat.com> (raw)
In-Reply-To: <20090418005257.1009549099@coco.kroah.org>
gregkh@suse.de wrote:
[...]
> From 15bd8021d870d2c4fbf8c16578d72d03cfddd3a7 Mon Sep 17 00:00:00 2001
> From: Steve French <sfrench@us.ibm.com>
> Date: Thu, 26 Mar 2009 23:05:15 +0000
> Subject: CIFS: Fix memory overwrite when saving nativeFileSystem field during mount
>
> upstream commit: b363b3304bcf68c4541683b2eff70b29f0446a5b
>
> CIFS can allocate a few bytes to little for the nativeFileSystem field
> during tree connect response processing during mount. This can result
> in a "Redzone overwritten" message to be logged.
The same for 2.6.28-stable tree.
On top of commit b363b330, we need:
f083def6 - cifs: fix buffer size for tcon->nativeFileSystem field
22c9d52b - cifs: remove unnedded bcc_ptr update in CIFSTCon
and maybe this too:
313fecfa - cifs: add cFYI messages with some of the saved strings from
ssetup/tcon
There is no CVE name for this yet. Still waiting.
Thanks, Eugene
--
Eugene Teo / Red Hat Security Response Team
parent reply other threads:[~2009-04-20 5:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090418005257.1009549099@coco.kroah.org>]
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=49EC06D1.7030208@redhat.com \
--to=eugene@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
--cc=shirishp@us.ibm.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=vinaysridhar@in.ibm.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).