linux-kernel - Re: [syzbot] [kernel?] linux-next test error: KASAN: slab-use-after-free Write in binder_add

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: <Z5LarLkj50YumVD1@google.com>
Date: Fri, 24 Jan 2025 00:11:24 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: syzbot <syzbot+7015dcf45953112c8b45@...kaller.appspotmail.com>
Cc: arve@...roid.com, brauner@...nel.org, gregkh@...uxfoundation.org,
	joel@...lfernandes.org, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, maco@...roid.com, sfr@...b.auug.org.au,
	surenb@...gle.com, syzkaller-bugs@...glegroups.com,
	tkjos@...roid.com
Subject: Re: [syzbot] [kernel?] linux-next test error: KASAN:
 slab-use-after-free Write in binder_add_device

On Thu, Jan 23, 2025 at 12:26:03PM -0800, syzbot wrote:
> Hello,
> 
> syzbot tried to test the proposed patch but the build/boot failed:
> 
> 0][   T52]  ieee80211_unregister_hw+0x5d/0x2c0
> [   72.827744][   T52]  mac80211_hwsim_del_radio+0x2c4/0x4c0
> [   72.827761][   T52]  ? __pfx_mac80211_hwsim_del_radio+0x10/0x10
> [   72.827777][   T52]  hwsim_exit_net+0x5c1/0x670
> [   72.827790][   T52]  ? __pfx_hwsim_exit_net+0x10/0x10
> [   72.827802][   T52]  ? __ip_vs_dev_cleanup_batch+0x239/0x260
> [   72.827818][   T52]  cleanup_net+0x812/0xd60
> [   72.827831][   T52]  ? __pfx_cleanup_net+0x10/0x10
> [   72.827847][   T52]  ? process_scheduled_works+0x976/0x1840
> [   72.827861][   T52]  process_scheduled_works+0xa66/0x1840
> [   72.827882][   T52]  ? __pfx_process_scheduled_works+0x10/0x10
> [   72.827898][   T52]  ? assign_work+0x364/0x3d0
> [   72.827913][   T52]  worker_thread+0x870/0xd30
> [   72.827931][   T52]  ? __kthread_parkme+0x169/0x1d0
> [   72.827946][   T52]  ? __pfx_worker_thread+0x10/0x10
> [   72.827960][   T52]  kthread+0x7a9/0x920
> [   72.827975][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.827991][   T52]  ? __pfx_worker_thread+0x10/0x10
> [   72.828004][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828019][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828035][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828057][   T52]  ? _raw_spin_unlock_irq+0x23/0x50
> [   72.828073][   T52]  ? lockdep_hardirqs_on+0x99/0x150
> [   72.828083][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828099][   T52]  ret_from_fork+0x4b/0x80
> [   72.828115][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828130][   T52]  ret_from_fork_asm+0x1a/0x30
> [   72.828147][   T52]  </TASK>

Huh? it sounds like linux-next is broken right now. This is some
unrelated lockdep issue. Let me retry with char-misc tree instead.