From: Marc Zyngier <maz@kernel.org>
To: cheung wall <zzqq0103.hey@gmail.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: memory leak in kvm_init_stage2_mmu
Date: Wed, 13 Mar 2024 15:54:07 +0000 [thread overview]
Message-ID: <87ttlap1pc.wl-maz@kernel.org> (raw)
In-Reply-To: <CAKHoSAtTA7pTi5T7oYZkNdVwt79sXbW+1=V=LZxpKdJGRSk0Eg@mail.gmail.com>
On Wed, 13 Mar 2024 04:53:52 +0000,
cheung wall <zzqq0103.hey@gmail.com> wrote:
>
> Hello,
>
> when using Syzkaller to fuzz the latest Linux Kernel arm64 version,
> the following crash
>
> was triggered on:
>
>
> HEAD commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a (tag: v6.7)
>
> git tree: upstream
>
> console output: https://pastebin.com/raw/MLVZbN01
This reports "Forbidden".
> kernel config: https://pastebin.com/raw/PFD96ZwE
# CONFIG_KVM is not set
How do you expect this to work?
>
> C reproducer: https://pastebin.com/raw/rHmMzvGt
>
> Syzlang reproducer: https://pastebin.com/raw/dAt714WD
>
>
> If you fix this issue, please add the following tag to the commit:
>
> Reported-by: Qiang Zhang <zzqq0103.hey@gmail.com>
>
> ----------------------------------------------------------
>
> 2024/03/05 18:24:34 executed programs: 0
> 2024/03/05 18:26:41 executed programs: 8
> BUG: memory leak
> unreferenced object 0xffff023ad74b8100 (size 128):
> comm "syz-executor.3", pid 3911, jiffies 4295149819 (age 22.132s)
> hex dump (first 32 bytes):
> 28 00 00 00 01 00 00 00 00 40 4e d7 3a 02 ff ff (........@N.:...
> 80 d9 5f a4 48 d3 ff ff c8 69 46 d7 3a 02 ff ff .._.H....iF.:...
> backtrace:
> [<000000008d295845>] kmemleak_alloc_recursive
> data/embfuzz/emblinux/linux-4a61839152cc3e9e00ac059d73a28d148d622b30/./include/linux/kmemleak.h:42
[...]
I suspect this report suffers from the same problem as the other one,
where this is actually against 6.1.61 rather than 6.7 as advertised?
I ran the reproducer locally on 6.8, and didn't observe any failure. I
had to modify the it though, as I'm using a host with 16kB page size.
Please let me know if I'm missing something.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-03-13 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 4:53 memory leak in kvm_init_stage2_mmu cheung wall
2024-03-13 15:54 ` Marc Zyngier [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=87ttlap1pc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
--cc=zzqq0103.hey@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).