From: Andrew Morton <akpm@linux-foundation.org>
To: Luka <luka.2016.cs@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] WARNING in shmem_rmdir in Linux kernel v6.12
Date: Tue, 3 Jun 2025 21:48:12 -0700 [thread overview]
Message-ID: <20250603214812.3c0e774ffa4700f47bd1340f@linux-foundation.org> (raw)
In-Reply-To: <CALm_T+1tHV6QmeykRwch602TzgJet+1dOWe25VSV6dw_Xo0SyQ@mail.gmail.com>
On Wed, 4 Jun 2025 12:43:01 +0800 Luka <luka.2016.cs@gmail.com> wrote:
> Dear Kernel Maintainers,
>
> I am writing to report a potential vulnerability identified in the
> upstream Linux Kernel version v6.12, corresponding to the following
> commit in the mainline repository:
>
> Git Commit: adc218676eef25575469234709c2d87185ca223a (tag: v6.12)
>
> This issue was discovered during the testing of the Android 16 AOSP
> kernel, which is based on Linux kernel version 6.12, specifically from
> the AOSP kernel branch:
>
> AOSP kernel branch: android16-6.12
> Manifest path: kernel/common.git
> Source URL: https://android.googlesource.com/kernel/common/+/refs/heads/android16-6.12
>
> Although this kernel branch is used in Android 16 development, its
> base is aligned with the upstream Linux v6.12 release. I observed this
> issue while conducting stability and fuzzing tests on the Android 16
> platform and identified that the root cause lies in the upstream
> codebase.
Please just include all the bug info in the email.
>
> Bug Location: shmem_rmdir+0x48/0x84 mm/shmem.c:3733
>
> Bug Report: https://hastebin.com/share/jazumewiya.css
>
> Entire Log: https://hastebin.com/share/uyuyaheken.perl
Those links don't work for me. "We're sorry, but the contents of the
bin could not be found, or it has been deleted"
prev parent reply other threads:[~2025-06-04 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 4:43 Luka
2025-06-04 4:48 ` Andrew Morton [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=20250603214812.3c0e774ffa4700f47bd1340f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luka.2016.cs@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