[BUG] unable to handle kernel paging request in process_one_work in Linux 6.12

[BUG] unable to handle kernel paging request in process_one_work in Linux 6.12

[Luka]

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.


Bug Location: process_one_work+0x474/0xd04 kernel/workqueue.c:3213

Bug Report: https://hastebin.com/share/yacupoheje.css

Entire Log: https://hastebin.com/share/inasotiyuz.perl


Thank you very much for your time and attention. I sincerely apologize
that I am currently unable to provide a reproducer for this issue.
However, I am actively working on reproducing the problem, and I will
make sure to share any findings or reproducing steps with you as soon
as they are available.

I greatly appreciate your efforts in maintaining the Linux kernel and
your attention to this matter.

Best regards,
Luka

Re: [BUG] unable to handle kernel paging request in process_one_work in Linux 6.12

[Al Viro]

On Wed, Jun 04, 2025 at 12:06:56PM +0800, Luka wrote:
> Bug Report: https://hastebin.com/share/yacupoheje.css
> 
> Entire Log: https://hastebin.com/share/inasotiyuz.perl
> 
> 
> Thank you very much for your time and attention. I sincerely apologize
> that I am currently unable to provide a reproducer for this issue.
> However, I am actively working on reproducing the problem, and I will
> make sure to share any findings or reproducing steps with you as soon
> as they are available.
> 
> I greatly appreciate your efforts in maintaining the Linux kernel and
> your attention to this matter.

On the off-chance you are for real: anything that requires any kind
of javashit interpreter is a non-starter.  I'm not wasting my time
decoding that "language" and I'm sure as hell not going to trust anything
browser-like to run code from an unknown source without getting buggered.
Ain't happening.

If you want that stuff to be looked at, post in plain text.