From: Hillf Danton <hdanton@sina.com>
To: Ubisectech Sirius <bugreport@ubisectech.com>
Cc: Eric Dumazet <edumazet@google.com>,
Shigeru Yoshida <syoshida@redhat.com>,
Suman Ghosh <sumang@marvell.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: BUG: unable to handle kernel paging request in __skb_flow_dissect
Date: Fri, 19 Jan 2024 21:01:41 +0800 [thread overview]
Message-ID: <20240119130141.2160-1-hdanton@sina.com> (raw)
In-Reply-To: <2c5794fb-c7cd-405a-8c63-f1820b8dbfaa.bugreport@ubisectech.com>
On Wed, 17 Jan 2024 15:32:28 +0800 Ubisectech Sirius <bugreport@ubisectech.com>
> Hello.
> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
> Recently, our team has discovered a issue in Linux kernel 6.7.0-g052d534373b7.
> Attached to the email were a POC file of the issue.
> Stack dump:
> [ 185.664167][ T8332] BUG: unable to handle page fault for address: ffffed1029c40001
> [ 185.665134][ T8332] #PF: supervisor read access in kernel mode
> [ 185.665877][ T8332] #PF: error_code(0x0000) - not-present page
> [ 185.666481][ T8332] PGD 7ffd0067 P4D 7ffd0067 PUD 3fff5067 PMD 0
> [ 185.667129][ T8332] Oops: 0000 [#1] PREEMPT SMP KASAN
> [ 185.667719][ T8332] CPU: 1 PID: 8332 Comm: poc Not tainted 6.7.0-g052d534373b7 #19
> [ 185.668641][ T8332] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
> [ 185.669639][ T8332] RIP: 0010:__skb_flow_dissect (net/core/flow_dissector.c:1170 (discriminator 1))
Looks like the syzbot report [1] on 01 Jan 2024, and decoding the test
result of a debug patch [2] is welcome.
Hillf
[1] https://lore.kernel.org/lkml/000000000000498a02060de59162@google.com/
[2] https://lore.kernel.org/lkml/00000000000078d073060f4b51e7@google.com/
prev parent reply other threads:[~2024-01-19 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 7:32 Ubisectech Sirius
2024-01-19 13:01 ` Hillf Danton [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=20240119130141.2160-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=bugreport@ubisectech.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sumang@marvell.com \
--cc=syoshida@redhat.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
all inboxes | Powered by JetHome®