From: Jan Kara <jack@suse.cz>
To: Mathias Krause <minipli@googlemail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix info leaks on export for udf and isofs
Date: Fri, 13 Jul 2012 14:10:09 +0200 [thread overview]
Message-ID: <20120713121009.GA20361@quack.suse.cz> (raw)
In-Reply-To: <1342075615-24683-1-git-send-email-minipli@googlemail.com>
On Thu 12-07-12 08:46:53, Mathias Krause wrote:
> Al, Jan,
>
> this patch set fixes info leaks in isofs and udf. Both file systems fail to
> initialize all bytes of the f_handle byte array when creating a handle for a
> path pointing to a directory. This memory gets copied to userland and that for
> is a leak of uninitialized heap data to userland that should be fixed.
>
> This info leak can be triggered locally by using the name_to_handle_at()
> syscall.
Thanks! I've merged both patches into my tree.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2012-07-13 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 6:46 Mathias Krause
2012-07-12 6:46 ` [PATCH 1/2] isofs: avoid info leak on export Mathias Krause
2012-07-12 6:46 ` [PATCH 2/2] udf: " Mathias Krause
2012-07-13 12:10 ` Jan Kara [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=20120713121009.GA20361@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=viro@zeniv.linux.org.uk \
/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®