From: Andrew Morton <akpm@linux-foundation.org>
To: Big Sleep <big-sleep-vuln-reports@google.com>
Cc: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: Oops in secretmem_fault()
Date: Thu, 30 Oct 2025 18:36:21 -0700 [thread overview]
Message-ID: <20251030183621.39ea843ebba82ae133b2b38b@linux-foundation.org> (raw)
In-Reply-To: <CAEXGt5QeDpiHTu3K9tvjUTPqo+d-=wuCNYPa+6sWKrdQJ-ATdg@mail.gmail.com>
On Thu, 30 Oct 2025 16:34:29 +0100 Big Sleep <big-sleep-vuln-reports@google.com> wrote:
> Hello Mike and Andrew,
>
> we found a bug in secretmem_fault() - please see below for details!
>
> --Google Big Sleep
Didn't know about this - it looks neat.
https://issuetracker.google.com/issues/430375499
: Big Sleep is a collaboration between Google Project Zero and Google
: DeepMind to build an agentic AI system to help automate software
: vulnerability research
>
> ## Reporter Credit
>
> Google Big Sleep
>
You might want to include a token here so we (you!) can track the
report through to its resolution. See what the sysbot people are
doing. For example,
https://lkml.rescloud.iu.edu/2408.2/07972.html included:
: IMPORTANT: if you fix the issue, please add the following tag to the commit:
: Reported-by: syzbot+5054473a31f78f735416@syzkaller.appspotmail.com
and when Dmitry fixed this he included that info in the patch metadata:
https://lore.kernel.org/all/20251028101447.693289-1-dmantipov@yandex.ru/T/#u
and that Reported-by: will be carried all the way into the mainline tree.
btw, it would be nice to Cc some human on these reports. One cannot
be very confident that emails sent to big-sleep-vuln-reports@google.com
will actually be read by someone.
next prev parent reply other threads:[~2025-10-31 1:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 15:34 Big Sleep
2025-10-31 1:36 ` Andrew Morton [this message]
2025-10-31 11:48 ` Big Sleep
2025-10-31 9:18 ` [PATCH 1/1] mm/secretmem: fix use-after-free race in fault handler Lance Yang
2025-10-31 9:59 ` Mike Rapoport
2025-10-31 10:19 ` David Hildenbrand
2025-10-31 10:35 ` Lance Yang
2025-10-31 10:24 ` Lorenzo Stoakes
2025-10-31 10:34 ` Lance Yang
2025-10-31 10:34 ` Lance Yang
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=20251030183621.39ea843ebba82ae133b2b38b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=big-sleep-vuln-reports@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=rppt@kernel.org \
--cc=willy@infradead.org \
/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®