From: Roman Gushchin <roman.gushchin@linux.dev>
To: Ubisectech Sirius <bugreport@ubisectech.com>
Cc: linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
hannes <hannes@cmpxchg.org>, mhocko <mhocko@kernel.org>,
"shakeel.butt" <shakeel.butt@linux.dev>
Subject: Re: general protection fault in refill_obj_stock
Date: Mon, 1 Apr 2024 16:52:24 -0700 [thread overview]
Message-ID: <ZgtIuBlUVE1Lj_Tc@P9FQF9L96D> (raw)
In-Reply-To: <91e1389e-0723-42e7-9ea4-396ec6b54e49.bugreport@ubisectech.com>
On Mon, Apr 01, 2024 at 03:04:46PM +0800, Ubisectech Sirius wrote:
> Hello.
> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec. Recently, our team has discovered a issue in Linux kernel 6.7. Attached to the email were a PoC file of the issue.
Thank you for the report!
I tried to compile and run your test program for about half an hour
on a virtual machine running 6.7 with enabled KASAN, but wasn't able
to reproduce the problem.
Can you, please, share a bit more information? How long does it take
to reproduce? Do you mind sharing your kernel config? Is there anything special
about your setup? What are exact steps to reproduce the problem?
Is this problem reproducible on 6.6?
It's interesting that the problem looks like use-after-free for the objcg pointer
but happens in the context of udev-systemd, which I believe should be fairly stable
and it's cgroup is not going anywhere.
Thanks!
next prev parent reply other threads:[~2024-04-01 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 7:04 general protection fault in refill_obj_stock Ubisectech Sirius
2024-04-01 23:52 ` Roman Gushchin [this message]
2024-04-02 1:50 ` 回复：general " Ubisectech Sirius
2024-04-02 2:55 ` Roman Gushchin
[not found] ` <69eeefa1-b654-4d19-b569-429abfc58d0a.bugreport@ubisectech.com>
2024-04-03 22:26 ` 回复：回复：general " Roman Gushchin
2024-04-04 22:46 ` Roman Gushchin
2024-04-14 4:19 ` 回复：general " Shakeel Butt
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=ZgtIuBlUVE1Lj_Tc@P9FQF9L96D \
--to=roman.gushchin@linux.dev \
--cc=bugreport@ubisectech.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
/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).