linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	marka@mediation.com, phind.uet@gmail.com,
	syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] memory leak in cap_inode_getsecurity
Date: Sun, 31 Jul 2022 08:12:27 -0700	[thread overview]
Message-ID: <000000000000b901a205e51b4f46@google.com> (raw)
In-Reply-To: <000000000000bdee330594070441@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    6a010258447d Merge tag 'for-linus' of git://git.armlinux.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15883fee080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2a1dcc1942e30704
dashboard link: https://syzkaller.appspot.com/bug?extid=942d5390db2d9624ced8
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1568846a080000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10f5e536080000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com

executing program
BUG: memory leak
unreferenced object 0xffff88810f0ac060 (size 32):
  comm "syz-executor240", pid 3622, jiffies 4294961303 (age 14.040s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff814c6ecd>] __do_krealloc mm/slab_common.c:1185 [inline]
    [<ffffffff814c6ecd>] krealloc+0x4d/0xb0 mm/slab_common.c:1218
    [<ffffffff8162625c>] vfs_getxattr_alloc+0x13c/0x1c0 fs/xattr.c:379
    [<ffffffff822374b2>] cap_inode_getsecurity+0xb2/0x500 security/commoncap.c:400
    [<ffffffff8223d88c>] security_inode_getsecurity+0x7c/0xb0 security/security.c:1441
    [<ffffffff81625a0a>] xattr_getsecurity fs/xattr.c:327 [inline]
    [<ffffffff81625a0a>] vfs_getxattr+0x22a/0x290 fs/xattr.c:423
    [<ffffffff81c0ab02>] ovl_xattr_get+0x62/0xa0 fs/overlayfs/inode.c:404
    [<ffffffff81624742>] __vfs_getxattr+0x72/0xa0 fs/xattr.c:401
    [<ffffffff82236f52>] cap_inode_need_killpriv+0x22/0x40 security/commoncap.c:301
    [<ffffffff8223d773>] security_inode_need_killpriv+0x23/0x60 security/security.c:1419
    [<ffffffff8161074e>] dentry_needs_remove_privs fs/inode.c:1992 [inline]
    [<ffffffff8161074e>] dentry_needs_remove_privs+0x4e/0xa0 fs/inode.c:1982
    [<ffffffff815cfead>] do_truncate+0x7d/0x130 fs/open.c:57
    [<ffffffff815d0169>] vfs_truncate+0x209/0x240 fs/open.c:111
    [<ffffffff815d0268>] do_sys_truncate.part.0+0xc8/0xe0 fs/open.c:134
    [<ffffffff815d0303>] do_sys_truncate fs/open.c:128 [inline]
    [<ffffffff815d0303>] __do_sys_truncate fs/open.c:146 [inline]
    [<ffffffff815d0303>] __se_sys_truncate fs/open.c:144 [inline]
    [<ffffffff815d0303>] __x64_sys_truncate+0x33/0x50 fs/open.c:144
    [<ffffffff845b1955>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff845b1955>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84600087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd



  reply	other threads:[~2022-07-31 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 19:59 memory leak in cap_inode_getsecurity syzbot
2022-07-31 15:12 ` syzbot [this message]
2022-08-01 10:11   ` [syzbot] " Miklos Szeredi
2022-08-01 10:29     ` syzbot
2022-08-01 12:20   ` Miklos Szeredi
2022-08-01 12:37     ` syzbot
2022-08-03  4:36 ` Miklos Szeredi
2022-08-03  4:53   ` [syzbot] " syzbot

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=000000000000b901a205e51b4f46@google.com \
    --to=syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marka@mediation.com \
    --cc=phind.uet@gmail.com \
    --cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).