All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6105ffc1ded71d194d6d@syzkaller.appspotmail.com>
To: dhowells@redhat.com, jarkko.sakkinen@kernel.org,
	jarkko@kernel.org,  jmorris@namei.org, keyrings@vger.kernel.org,
	lhenriques@suse.de,  linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,  paul@paul-moore.com,
	serge@hallyn.com, surajsonawane0215@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [keyrings?] [lsm?] KASAN: slab-use-after-free Read in key_put
Date: Tue, 19 Nov 2024 02:36:02 -0800	[thread overview]
Message-ID: <673c6a12.050a0220.87769.006b.GAE@google.com> (raw)
In-Reply-To: <673b6aec.050a0220.87769.004a.GAE@google.com>

syzbot has bisected this issue to:

commit 9578e327b2b4935a25d49e3891b8fcca9b6c10c6
Author: Luis Henriques <lhenriques@suse.de>
Date:   Tue Jan 30 10:13:44 2024 +0000

    keys: update key quotas in key_put()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10821bf7980000
start commit:   adc218676eef Linux 6.12
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=12821bf7980000
console output: https://syzkaller.appspot.com/x/log.txt?x=14821bf7980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=55f8591b98dd132
dashboard link: https://syzkaller.appspot.com/bug?extid=6105ffc1ded71d194d6d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12dbbb5f980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11c672e8580000

Reported-by: syzbot+6105ffc1ded71d194d6d@syzkaller.appspotmail.com
Fixes: 9578e327b2b4 ("keys: update key quotas in key_put()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2024-11-19 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 16:27 [syzbot] [keyrings?] [lsm?] KASAN: slab-use-after-free Read in key_put syzbot
2024-11-18 21:27 ` Suraj Sonawane
2024-11-18 21:37   ` syzbot
2024-11-19 10:36 ` syzbot [this message]
2024-11-20 10:42 ` Hillf Danton
2024-11-20 11:15   ` syzbot
2025-03-19 15:20 ` David Howells
2025-03-19 15:49   ` 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=673c6a12.050a0220.87769.006b.GAE@google.com \
    --to=syzbot+6105ffc1ded71d194d6d@syzkaller.appspotmail.com \
    --cc=dhowells@redhat.com \
    --cc=jarkko.sakkinen@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=jmorris@namei.org \
    --cc=keyrings@vger.kernel.org \
    --cc=lhenriques@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    --cc=surajsonawane0215@gmail.com \
    --cc=syzkaller-bugs@googlegroups.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 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.