From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>,
Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"John Johansen" <john.johansen@canonical.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Salvatore Mesoraca" <s.mesoraca16@gmail.com>
Subject: Re: [GIT PULL] blob-stacking updates for security-next
Date: Fri, 11 Jan 2019 19:38:33 +0900 [thread overview]
Message-ID: <ce79cdd5-3020-8901-a5a4-ec42005734fd@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20190108213504.GA32901@beast>
On 2019/01/09 6:35, Kees Cook wrote:
> Hi James,
>
> Please pull these blob-stacking changes for security-next.
>
> Thanks!
>
> -Kees
>
> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>
> Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/blob-stacking-security-next
>
> for you to fetch changes up to a5e2fe7ede1268d2f80fe49ca1f717d0e3750995:
>
> TOMOYO: Update LSM flags to no longer be exclusive (2019-01-08 13:18:45 -0800)
>
And syzbot already found a bug.
This is occurring immediately after memory allocation failure for cred object.
We need to be prepared for free() function being called when alloc() function failed.
[ 59.992498][ T8010] FAULT_INJECTION: forcing a failure.
[ 59.992498][ T8010] name failslab, interval 1, probability 0, space 0, times 1
[ 60.005214][ T8010] CPU: 0 PID: 8010 Comm: syz-executor178 Not tainted 5.0.0-rc1-next-20190111 #10
[ 60.014337][ T8010] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
[ 60.024383][ T8010] Call Trace:
[ 60.027657][ T8010] dump_stack+0x1db/0x2d0
[ 60.063731][ T8010] should_fail.cold+0xa/0x14
[ 60.089894][ T8010] __should_failslab+0x121/0x190
[ 60.094810][ T8010] should_failslab+0x9/0x14
[ 60.099411][ T8010] __kmalloc+0x2dc/0x740
[ 60.124293][ T8010] security_prepare_creds+0x123/0x190
[ 60.129644][ T8010] prepare_creds+0x3c4/0x510
[ 60.149852][ T8010] __x64_sys_capset+0x58c/0x9b0
[ 60.185347][ T8010] do_syscall_64+0x1a3/0x800
[ 60.206747][ T8010] entry_SYSCALL_64_after_hwframe+0x49/0xbe
next prev parent reply other threads:[~2019-01-11 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:35 [GIT PULL] blob-stacking updates for security-next Kees Cook
2019-01-10 20:34 ` James Morris
2019-01-10 21:21 ` Paul Moore
2019-01-10 22:00 ` James Morris
2019-01-10 22:39 ` Paul Moore
2019-01-11 10:38 ` Tetsuo Handa [this message]
2019-01-11 17:29 ` Casey Schaufler
2019-01-11 17:44 ` Kees Cook
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=ce79cdd5-3020-8901-a5a4-ec42005734fd@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=s.mesoraca16@gmail.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).