From: <gregkh@linuxfoundation.org>
To: sbauer@plzdonthack.me, gregkh@linuxfoundation.org,
torvalds@linux-foundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "vfs: ioctl: prevent double-fetch in dedupe ioctl" has been added to the 4.7-stable tree
Date: Mon, 08 Aug 2016 20:01:57 +0200 [thread overview]
Message-ID: <14706793178649@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
vfs: ioctl: prevent double-fetch in dedupe ioctl
to the 4.7-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
vfs-ioctl-prevent-double-fetch-in-dedupe-ioctl.patch
and it can be found in the queue-4.7 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 10eec60ce79187686e052092e5383c99b4420a20 Mon Sep 17 00:00:00 2001
From: Scott Bauer <sbauer@plzdonthack.me>
Date: Wed, 27 Jul 2016 19:11:29 -0600
Subject: vfs: ioctl: prevent double-fetch in dedupe ioctl
From: Scott Bauer <sbauer@plzdonthack.me>
commit 10eec60ce79187686e052092e5383c99b4420a20 upstream.
This prevents a double-fetch from user space that can lead to to an
undersized allocation and heap overflow.
Fixes: 54dbc1517237 ("vfs: hoist the btrfs deduplication ioctl to the vfs")
Signed-off-by: Scott Bauer <sbauer@plzdonthack.me>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/ioctl.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/ioctl.c
+++ b/fs/ioctl.c
@@ -590,6 +590,7 @@ static long ioctl_file_dedupe_range(stru
goto out;
}
+ same->dest_count = count;
ret = vfs_dedupe_file_range(file, same);
if (ret)
goto out;
Patches currently in stable-queue which might be from sbauer@plzdonthack.me are
queue-4.7/vfs-ioctl-prevent-double-fetch-in-dedupe-ioctl.patch
reply other threads:[~2016-08-08 18:01 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=14706793178649@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=sbauer@plzdonthack.me \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.