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>] [day] [month] [year] [list]
Message-ID: <681dfa4e.050a0220.a19a9.0131.GAE@google.com>
Date: Fri, 09 May 2025 05:51:26 -0700
From: syzbot <syzbot+4ebd710a879482a93f8f@...kaller.appspotmail.com>
To: catalin.marinas@....com, joey.gouly@....com, kvm@...r.kernel.org, 
	kvmarm@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org, 
	linux-kernel@...r.kernel.org, maz@...nel.org, oliver.upton@...ux.dev, 
	suzuki.poulose@....com, syzkaller-bugs@...glegroups.com, will@...nel.org, 
	yuzenghui@...wei.com
Subject: [syzbot] [kvm?] [kvmarm?] BUG: unable to handle kernel paging request
 in vgic_its_save_tables_v0

Hello,

syzbot found the following issue on:

HEAD commit:    c4e91ea0cc7e Merge branch kvm-arm64/misc-6.16 into kvmarm-..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next
console output: https://syzkaller.appspot.com/x/log.txt?x=11d634f4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2f705363127f7638
dashboard link: https://syzkaller.appspot.com/bug?extid=4ebd710a879482a93f8f
compiler:       Debian clang version 20.1.3 (++20250415083350+2131242240f7-1~exp1~20250415203523.103), Debian LLD 20.1.3
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1437c4d4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12f84768580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/fa3fbcfdac58/non_bootable_disk-c4e91ea0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ecf29c15547/vmlinux-c4e91ea0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/59a7b6f25d98/Image-c4e91ea0.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4ebd710a879482a93f8f@...kaller.appspotmail.com

Unable to handle kernel paging request at virtual address ffef800000000001
KASAN: maybe wild-memory-access in range [0xff00000000000010-0xff0000000000001f]
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
  CM = 0, WnR = 0, TnD = 0, TagAccess = 0
  GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[ffef800000000001] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 3370 Comm: syz-executor338 Not tainted 6.15.0-rc4-syzkaller-gc4e91ea0cc7e #0 PREEMPT 
Hardware name: linux,dummy-virt (DT)
pstate: 61402009 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
pc : vgic_its_save_ite arch/arm64/kvm/vgic/vgic-its.c:2145 [inline]
pc : vgic_its_save_itt arch/arm64/kvm/vgic/vgic-its.c:2248 [inline]
pc : vgic_its_save_device_tables arch/arm64/kvm/vgic/vgic-its.c:2394 [inline]
pc : vgic_its_save_tables_v0+0x3e0/0xe38 arch/arm64/kvm/vgic/vgic-its.c:2614
lr : compute_next_eventid_offset arch/arm64/kvm/vgic/vgic-its.c:2061 [inline]
lr : vgic_its_save_ite arch/arm64/kvm/vgic/vgic-its.c:2142 [inline]
lr : vgic_its_save_itt arch/arm64/kvm/vgic/vgic-its.c:2248 [inline]
lr : vgic_its_save_device_tables arch/arm64/kvm/vgic/vgic-its.c:2394 [inline]
lr : vgic_its_save_tables_v0+0x37c/0xe38 arch/arm64/kvm/vgic/vgic-its.c:2614
sp : ffff80008ecd7bf0
x29: ffff80008ecd7c70 x28: 66f00000123bb4f0 x27: 0000000000000000
x26: 000000000000002e x25: 00000000fffffdfd x24: ccf0000013a2ac40
x23: 66f00000123bb438 x22: edf0000013a2a4d0 x21: edf0000013a2a4d0
x20: cdf0000012236600 x19: efff800000000000 x18: 0000000000000000
x17: 0000000000000032 x16: ffff800080011d9c x15: 0000000020000300
x14: 0000000000000000 x13: fff0000015703b08 x12: 0ff0000000000001
x11: 0000000000000010 x10: 0000000000002000 x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff80008021fbf4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800080158ffc
x2 : ffff80008021fc70 x1 : edf0000013a2a4d0 x0 : 0000000000000000
Call trace:
 vgic_its_save_ite arch/arm64/kvm/vgic/vgic-its.c:2145 [inline] (P)
 vgic_its_save_itt arch/arm64/kvm/vgic/vgic-its.c:2248 [inline] (P)
 vgic_its_save_device_tables arch/arm64/kvm/vgic/vgic-its.c:2394 [inline] (P)
 vgic_its_save_tables_v0+0x3e0/0xe38 arch/arm64/kvm/vgic/vgic-its.c:2614 (P)
 vgic_its_ctrl arch/arm64/kvm/vgic/vgic-its.c:-1 [inline]
 vgic_its_set_attr+0x544/0x828 arch/arm64/kvm/vgic/vgic-its.c:2777
 kvm_device_ioctl_attr virt/kvm/kvm_main.c:4639 [inline]
 kvm_device_ioctl+0x354/0x418 virt/kvm/kvm_main.c:-1
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:906 [inline]
 __se_sys_ioctl fs/ioctl.c:892 [inline]
 __arm64_sys_ioctl+0x18c/0x244 fs/ioctl.c:892
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x90/0x2b4 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x180/0x2f4 arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x58/0x74 arch/arm64/kernel/syscall.c:151
 el0_svc+0x58/0x134 arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
Code: 9100412b b2481d69 d344fd2c d378fd69 (386c6a6c) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	9100412b 	add	x11, x9, #0x10
   4:	b2481d69 	orr	x9, x11, #0xff00000000000000
   8:	d344fd2c 	lsr	x12, x9, #4
   c:	d378fd69 	lsr	x9, x11, #56
* 10:	386c6a6c 	ldrb	w12, [x19, x12] <-- 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@...glegroups.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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ