All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-kernel@vger.kernel.org, mingo@redhat.com,
	 syzkaller-bugs@googlegroups.com, tglx@kernel.org,
	x86@kernel.org
Subject: [syzbot] [kernel?] KMSAN: uninit-value in decay_va_pool_node
Date: Wed, 01 Apr 2026 22:31:18 -0700	[thread overview]
Message-ID: <69cdff26.050a0220.2dbe29.0001.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    be762d8b6dd7 Merge tag 'hwmon-for-v7.0-rc6' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10755cba580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=963de479f54c6dbb
dashboard link: https://syzkaller.appspot.com/bug?extid=37b7f6cd519f7fb8d32a
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0594908a4960/disk-be762d8b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ddd66865f6c/vmlinux-be762d8b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dc2e48fdbf6e/bzImage-be762d8b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com

=====================================================
BUG: KMSAN: uninit-value in __list_del_entry_valid include/linux/list.h:-1 [inline]
BUG: KMSAN: uninit-value in __list_del_entry include/linux/list.h:223 [inline]
BUG: KMSAN: uninit-value in list_del_init include/linux/list.h:295 [inline]
BUG: KMSAN: uninit-value in decay_va_pool_node+0xf78/0x1dd0 mm/vmalloc.c:2255
 __list_del_entry_valid include/linux/list.h:-1 [inline]
 __list_del_entry include/linux/list.h:223 [inline]
 list_del_init include/linux/list.h:295 [inline]
 decay_va_pool_node+0xf78/0x1dd0 mm/vmalloc.c:2255
 __purge_vmap_area_lazy+0x1a1/0x1500 mm/vmalloc.c:2361
 _vm_unmap_aliases+0x134c/0x1490 mm/vmalloc.c:2996
 vm_reset_perms+0x625/0x900 mm/vmalloc.c:3388
 vfree+0x463/0xa10 mm/vmalloc.c:3467
 bpf_prog_free_deferred+0xc12/0xc80 kernel/bpf/core.c:-1
 process_one_work kernel/workqueue.c:3276 [inline]
 process_scheduled_works+0xb82/0x1e80 kernel/workqueue.c:3359
 worker_thread+0xee4/0x1590 kernel/workqueue.c:3440
 kthread+0x53f/0x600 kernel/kthread.c:436
 ret_from_fork+0x20f/0x910 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

Uninit was stored to memory at:
 __list_del_entry_valid include/linux/list.h:127 [inline]
 __list_del_entry include/linux/list.h:223 [inline]
 list_del_init include/linux/list.h:295 [inline]
 decay_va_pool_node+0xf71/0x1dd0 mm/vmalloc.c:2255
 __purge_vmap_area_lazy+0x1a1/0x1500 mm/vmalloc.c:2361
 _vm_unmap_aliases+0x134c/0x1490 mm/vmalloc.c:2996
 vm_reset_perms+0x625/0x900 mm/vmalloc.c:3388
 vfree+0x463/0xa10 mm/vmalloc.c:3467
 bpf_prog_free_deferred+0xc12/0xc80 kernel/bpf/core.c:-1
 process_one_work kernel/workqueue.c:3276 [inline]
 process_scheduled_works+0xb82/0x1e80 kernel/workqueue.c:3359
 worker_thread+0xee4/0x1590 kernel/workqueue.c:3440
 kthread+0x53f/0x600 kernel/kthread.c:436
 ret_from_fork+0x20f/0x910 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

Uninit was created at:
 slab_post_alloc_hook mm/slub.c:4545 [inline]
 slab_alloc_node mm/slub.c:4866 [inline]
 kmem_cache_alloc_node_noprof+0x3cd/0x12d0 mm/slub.c:4918
 alloc_vmap_area+0x327/0x2e30 mm/vmalloc.c:2065
 __get_vm_area_node+0x263/0x3b0 mm/vmalloc.c:3232
 __vmalloc_node_range_noprof+0x44a/0x2d80 mm/vmalloc.c:4024
 __vmalloc_node_noprof mm/vmalloc.c:4124 [inline]
 vzalloc_noprof+0xce/0x140 mm/vmalloc.c:4202
 alloc_counters+0x7c/0x8a0 net/ipv4/netfilter/ip_tables.c:799
 copy_entries_to_user net/ipv6/netfilter/ip6_tables.c:837 [inline]
 get_entries net/ipv6/netfilter/ip6_tables.c:1039 [inline]
 do_ip6t_get_ctl+0xab1/0x1fc0 net/ipv6/netfilter/ip6_tables.c:1677
 nf_getsockopt+0x497/0x4f0 net/netfilter/nf_sockopt.c:116
 ipv6_getsockopt+0x323/0x4c0 net/ipv6/ipv6_sockglue.c:1473
 tcp_getsockopt+0x174/0x1a0 net/ipv4/tcp.c:4894
 sock_common_getsockopt+0x9c/0xf0 net/core/sock.c:3946
 do_sock_getsockopt+0x3a8/0x4c0 net/socket.c:2383
 __sys_getsockopt net/socket.c:2412 [inline]
 __do_sys_getsockopt net/socket.c:2419 [inline]
 __se_sys_getsockopt net/socket.c:2416 [inline]
 __x64_sys_getsockopt+0x32d/0x520 net/socket.c:2416
 x64_sys_call+0x3ab8/0x3ea0 arch/x86/include/generated/asm/syscalls_64.h:56
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x134/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

CPU: 0 UID: 0 PID: 7227 Comm: kworker/0:8 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: events bpf_prog_free_deferred

=====================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2026-04-02  5:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69cdff26.050a0220.2dbe29.0001.GAE@google.com \
    --to=syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.