From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: vegard.nossum@oracle.com
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 5/9] hfsplus: Known exploit detection for CVE-2012-2319
Date: Fri, 13 Dec 2013 11:14:03 +0000 [thread overview]
Message-ID: <20131213111403.77a8122c@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1386867152-24072-5-git-send-email-vegard.nossum@oracle.com>
On Thu, 12 Dec 2013 17:52:28 +0100
vegard.nossum@oracle.com wrote:
> From: Vegard Nossum <vegard.nossum@oracle.com>
>
> See 6f24f892871acc47b40dd594c63606a17c714f77.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
> ---
> fs/hfsplus/catalog.c | 2 ++
> fs/hfsplus/dir.c | 3 +++
> 2 files changed, 5 insertions(+)
>
> diff --git a/fs/hfsplus/catalog.c b/fs/hfsplus/catalog.c
> index 968ce41..5f47a1a 100644
> --- a/fs/hfsplus/catalog.c
> +++ b/fs/hfsplus/catalog.c
> @@ -8,6 +8,7 @@
> * Handling of catalog records
> */
>
> +#include <linux/exploit.h>
>
> #include "hfsplus_fs.h"
> #include "hfsplus_raw.h"
> @@ -374,6 +375,7 @@ int hfsplus_rename_cat(u32 cnid,
> if (err)
> goto out;
> if (src_fd.entrylength > sizeof(entry) || src_fd.entrylength < 0) {
> + exploit("CVE-2012-2319");
Whooppee but if I drive the box totally out of memory with several of
these file systems I can cause all sorts of problems due to missing null
checks, and I can feed some others such as reiserfs (why do we still ship
that ?) corrupt disk images and patch the kernel that way.
So surely we ought to be fixing the actual bugs first ?
Alan
next prev parent reply other threads:[~2013-12-13 11:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:52 [PATCH 1/9] Known exploit detection vegard.nossum
2013-12-12 16:52 ` [PATCH 2/9] exploit: report to audit subsystem when available vegard.nossum
2013-12-12 16:52 ` [PATCH 3/9] hfs: Known exploit detection for CVE-2011-4330 vegard.nossum
2013-12-13 8:00 ` Dan Carpenter
2013-12-12 16:52 ` [PATCH 4/9] net: Known exploit detection for CVE-2012-2136 vegard.nossum
2013-12-12 16:52 ` [PATCH 5/9] hfsplus: Known exploit detection for CVE-2012-2319 vegard.nossum
2013-12-13 1:40 ` Greg Kroah-Hartman
2013-12-13 11:14 ` One Thousand Gnomes [this message]
2013-12-12 16:52 ` [PATCH 6/9] x86: Known exploit detection for CVE-2013-0268 vegard.nossum
2013-12-12 16:52 ` [PATCH 7/9] drm/i915: Known exploit detection for CVE-2013-0913 vegard.nossum
2013-12-12 16:52 ` [PATCH 8/9] userns: Known exploit detection for CVE-2013-1959 vegard.nossum
2013-12-12 16:52 ` [PATCH 9/9] perf: Known exploit detection for CVE-2013-2094 vegard.nossum
2013-12-12 19:06 ` [PATCH 1/9] Known exploit detection Theodore Ts'o
2013-12-12 21:13 ` Kees Cook
2013-12-12 23:50 ` Ryan Mallon
2013-12-12 23:55 ` Kees Cook
2013-12-13 11:10 ` One Thousand Gnomes
2013-12-13 14:21 ` Jiri Kosina
2013-12-13 9:20 ` Vegard Nossum
2013-12-13 22:49 ` Ryan Mallon
2013-12-13 13:06 ` Ingo Molnar
2013-12-13 15:55 ` Jason Cooper
2013-12-13 23:07 ` Ryan Mallon
2013-12-13 0:25 ` Dave Jones
2013-12-13 0:45 ` Andy Lutomirski
2013-12-13 1:42 ` Greg Kroah-Hartman
2013-12-13 1:44 ` Dave Jones
2013-12-13 5:09 ` James Morris
2013-12-13 5:46 ` Theodore Ts'o
2013-12-13 13:19 ` Ingo Molnar
2013-12-13 10:21 ` Vegard Nossum
2013-12-13 10:31 ` Alexander Holler
2013-12-13 11:48 ` Dan Carpenter
2013-12-13 11:57 ` Greg Kroah-Hartman
2013-12-13 13:23 ` Ingo Molnar
2013-12-13 18:00 ` Kees Cook
2013-12-13 17:58 ` Kees Cook
2013-12-13 18:14 ` Linus Torvalds
2013-12-13 18:37 ` Kees Cook
2013-12-13 5:27 ` Theodore Ts'o
2013-12-13 9:32 ` Jiri Kosina
2013-12-13 18:07 ` Kees Cook
2013-12-13 9:12 ` Vegard Nossum
2013-12-13 13:27 ` Ingo Molnar
2013-12-13 8:20 ` Vegard Nossum
2013-12-14 23:59 ` Ryan Mallon
2013-12-13 12:54 ` Ingo Molnar
2013-12-16 5:17 ` Sasha Levin
2013-12-19 6:14 ` David Rientjes
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=20131213111403.77a8122c@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@oracle.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
all inboxes | Powered by JetHome®