From: syzbot <syzbot+9831d4affe35bb65b891@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Unable to handle kernel write to read-only memory at virtual address ADDR
Date: Mon, 26 Sep 2022 09:43:42 -0700 [thread overview]
Message-ID: <000000000000fe202005e9973a6b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c194837ebb57 Merge branch 'for-next/core', remote-tracking..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=144f9ca8880000
kernel config: https://syzkaller.appspot.com/x/.config?x=15a770deac0c935a
dashboard link: https://syzkaller.appspot.com/bug?extid=9831d4affe35bb65b891
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d8f5c4880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164dc2a8880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8d8ae425e7fa/disk-c194837e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c540d501ebe7/vmlinux-c194837e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9831d4affe35bb65b891@syzkaller.appspotmail.com
Unable to handle kernel write to read-only memory at virtual address ffff80000cb9e7b5
Mem abort info:
ESR = 0x000000009600004e
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x0e: level 2 permission fault
Data abort info:
ISV = 0, ISS = 0x0000004e
CM = 0, WnR = 1
swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000001c566a000
[ffff80000cb9e7b5] pgd=100000023ffff003, p4d=100000023ffff003, pud=100000023fffe003, pmd=00600001c5000781
Internal error: Oops: 000000009600004e [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 2561 Comm: udevd Not tainted 6.0.0-rc6-syzkaller-17742-gc194837ebb57 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __memset+0x50/0x188
lr : slab_post_alloc_hook mm/slab.h:729 [inline]
lr : slab_alloc_node mm/slub.c:3243 [inline]
lr : __kmalloc_node_track_caller+0x2bc/0x3bc mm/slub.c:4955
sp : ffff800016a33920
x29: ffff800016a33930 x28: ffff0000c9534f80 x27: 0000000000000000
x26: 000000000fffffff x25: ffff80000cb9e7b5 x24: 0000000000000000
x23: ffff0000c0001400 x22: ffff8000096b34f4 x21: 0000000000000200
x20: 0000000000082cc0 x19: 00000000ffffffff x18: 0000000000000000
x17: 0000000000000000 x16: ffff80000db49158 x15: ffff0000c9534f80
x14: 0000000000000010 x13: 0000000000000000 x12: ffff0000c9534f80
x11: 0000000000000001 x10: ffff80000d309000 x9 : 0000000000080800
x8 : ffff80000cb9e7b5 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 000000000000000b x3 : 000000000002b678
x2 : 0000000000000200 x1 : 0000000000000000 x0 : ffff80000cb9e7b5
Call trace:
__memset+0x50/0x188
kmalloc_reserve net/core/skbuff.c:362 [inline]
__alloc_skb+0x198/0x378 net/core/skbuff.c:434
alloc_skb include/linux/skbuff.h:1257 [inline]
alloc_uevent_skb+0x5c/0xd8 lib/kobject_uevent.c:290
uevent_net_broadcast_untagged+0xa0/0x1cc lib/kobject_uevent.c:326
kobject_uevent_net_broadcast+0x14c/0x1f8 lib/kobject_uevent.c:409
kobject_uevent_env+0x428/0x5ec lib/kobject_uevent.c:593
kobject_synth_uevent+0x354/0x6a4 lib/kobject_uevent.c:208
uevent_store+0x34/0x80 drivers/base/core.c:2509
dev_attr_store+0x4c/0x70 drivers/base/core.c:2211
sysfs_kf_write+0xf4/0x11c fs/sysfs/file.c:136
kernfs_fop_write_iter+0x1e4/0x294 fs/kernfs/file.c:354
call_write_iter include/linux/fs.h:2187 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x2dc/0x46c fs/read_write.c:578
ksys_write+0xb4/0x160 fs/read_write.c:631
__do_sys_write fs/read_write.c:643 [inline]
__se_sys_write fs/read_write.c:640 [inline]
__arm64_sys_write+0x24/0x34 fs/read_write.c:640
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190
Code: d65f03c0 cb0803e4 f2400c84 54000080 (a9001d07)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d65f03c0 ret
4: cb0803e4 neg x4, x8
8: f2400c84 ands x4, x4, #0xf
c: 54000080 b.eq 0x1c // b.none
* 10: a9001d07 stp x7, x7, [x8] <-- trapping instruction
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2022-09-26 17:27 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=000000000000fe202005e9973a6b@google.com \
--to=syzbot+9831d4affe35bb65b891@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.