From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: dan.j.rosenberg@gmail.com, aelder@sgi.com, stable@kernel.org
Subject: + xfs-prevent-reading-uninitialized-stack-memory.patch added to -mm tree
Date: Wed, 08 Sep 2010 14:55:29 -0700 [thread overview]
Message-ID: <201009082155.o88LtT2H012054@imap1.linux-foundation.org> (raw)
The patch titled
xfs: prevent reading uninitialized stack memory
has been added to the -mm tree. Its filename is
xfs-prevent-reading-uninitialized-stack-memory.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: xfs: prevent reading uninitialized stack memory
From: Dan Rosenberg <dan.j.rosenberg@gmail.com>
The XFS_IOC_FSGETXATTR ioctl allows unprivileged users to read 12 bytes of
uninitialized stack memory, because the fsxattr struct declared on the
stack in xfs_ioc_fsgetxattr() does not alter (or zero) the 12-byte fsx_pad
member before copying it back to the user. This patch takes care of it.
Signed-off-by: Dan Rosenberg <dan.j.rosenberg@gmail.com>
Cc: Alex Elder <aelder@sgi.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/xfs/linux-2.6/xfs_ioctl.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN fs/xfs/linux-2.6/xfs_ioctl.c~xfs-prevent-reading-uninitialized-stack-memory fs/xfs/linux-2.6/xfs_ioctl.c
--- a/fs/xfs/linux-2.6/xfs_ioctl.c~xfs-prevent-reading-uninitialized-stack-memory
+++ a/fs/xfs/linux-2.6/xfs_ioctl.c
@@ -785,6 +785,8 @@ xfs_ioc_fsgetxattr(
{
struct fsxattr fa;
+ memset(&fa, 0, sizeof(struct fsxattr));
+
xfs_ilock(ip, XFS_ILOCK_SHARED);
fa.fsx_xflags = xfs_ip2xflags(ip);
fa.fsx_extsize = ip->i_d.di_extsize << ip->i_mount->m_sb.sb_blocklog;
_
Patches currently in -mm which might be from dan.j.rosenberg@gmail.com are
xfs-prevent-reading-uninitialized-stack-memory.patch
reply other threads:[~2010-09-08 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201009082155.o88LtT2H012054@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aelder@sgi.com \
--cc=dan.j.rosenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stable@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