linux-kernel - Re: BUG: INFO: trying to register non-static key in call_timer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87cylm76f1.ffs@tglx>
Date: Mon, 02 Sep 2024 11:26:26 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Xingyu Li <xli399@....edu>, anna-maria@...utronix.de,
 frederic@...nel.org, linux-kernel@...r.kernel.org, Yu Hao
 <yhao016@....edu>, Tejun Heo <tj@...nel.org>
Subject: Re: BUG: INFO: trying to register non-static key in call_timer_fn

On Wed, Aug 28 2024 at 17:16, Xingyu Li wrote:
> We found a bug in Linux 6.10 using syzkaller. It is possibly a
> corrupted list  bug.
> The reproducer is
> https://gist.github.com/freexxxyyy/4c465c7d81957779d8bdea44f6cb8977

Again. Without exact kernel version, config and reproduction
instructions this is not really helpful.

> The bug report is:
>
> Syzkaller hit 'INFO: trying to register non-static key in call_timer_fn' bug.
>
> INFO: trying to register non-static key.
> The code is fine but needs lockdep annotation, or maybe
> you didn't initialize this object before use?

That's simply not possible.

> list_add corruption. prev is NULL.

> Call Trace:
>  <IRQ>
>  __list_add_valid include/linux/list.h:88 [inline]
>  __list_add include/linux/list.h:150 [inline]
>  list_add_tail include/linux/list.h:183 [inline]
>  insert_work+0x114/0x320 kernel/workqueue.c:2212
>  __queue_work+0xb61/0xce0 kernel/workqueue.c:2360
>  queue_work_on+0x18a/0x2d0 kernel/workqueue.c:2411

So that looks similar to the other unexplainable report

  https://lore.kernel.org/all/CALAgD-7TsMdA7rjxfpheXc=MNqikEXY9TZNxJt4z9vm6Yfs5qQ@mail.gmail.com

and smells like memory corruption of some sort, which then triggers
non-sensical issues in other code.

Thanks,

        tglx