From: syzbot <syzbot+461576769f21a04b4bc0@syzkaller.appspotmail.com>
To: lenb@kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, pavel@kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [pm?] KASAN: invalid-access Read in swsusp_save
Date: Thu, 08 Oct 2026 18:03:28 -0700 [thread overview]
Message-ID: <6ac83d60.8cdf6287.1eb53.0040.GAE@google.com> (raw)
In-Reply-To: <6a6b59ed.57649fcc.360844.0019.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 0c2669a9f4a1 Merge tag 'soc-fixes-7.3-2' of git://git.kern..
git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux master
console output: https://syzkaller.appspot.com/x/log.txt?x=14e881d1580000
kernel config: https://syzkaller.appspot.com/x/.config?x=644925403e5fc5f8
dashboard link: https://syzkaller.appspot.com/bug?extid=461576769f21a04b4bc0
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e881d1580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=170e4671580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/fa3fbcfdac58/non_bootable_disk-0c2669a9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/97ac54fdda4f/vmlinux-0c2669a9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bc86cb1e5945/Image-0c2669a9.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+461576769f21a04b4bc0@syzkaller.appspotmail.com
printk: Suspending console(s) (use no_console_suspend to debug)
Disabling non-boot CPUs ...
psci: CPU1 killed (polled 0 ms)
hibernate: Saved 0 MTE pages
==================================================================
BUG: KASAN: invalid-access in do_copy_page kernel/power/snapshot.c:1436 [inline]
BUG: KASAN: invalid-access in safe_copy_page kernel/power/snapshot.c:1457 [inline]
BUG: KASAN: invalid-access in copy_data_page kernel/power/snapshot.c:1508 [inline]
BUG: KASAN: invalid-access in copy_data_pages kernel/power/snapshot.c:1543 [inline]
BUG: KASAN: invalid-access in swsusp_save+0x2d4/0x5a0 kernel/power/snapshot.c:2133
Read at addr f7f0000003c1f100 by task syz.3.18/3725
Pointer tag: [f7], memory tag: [fe]
CPU: 0 UID: 0 PID: 3725 Comm: syz.3.18 Not tainted syzkaller #0 PREEMPT
Hardware name: linux,dummy-virt (DT)
Call trace:
dump_backtrace arch/arm64/kernel/stacktrace.c:498 [inline] (C)
show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x60/0x80 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0x1c4/0x4b0 mm/kasan/report.c:482
kasan_report+0x84/0xac mm/kasan/report.c:595
report_tag_fault arch/arm64/mm/fault.c:372 [inline]
do_tag_recovery arch/arm64/mm/fault.c:384 [inline]
__do_kernel_fault+0x1b4/0x220 arch/arm64/mm/fault.c:428
do_bad_area+0x68/0x80 arch/arm64/mm/fault.c:533
do_tag_check_fault+0x34/0x44 arch/arm64/mm/fault.c:913
do_mem_abort+0x40/0x90 arch/arm64/mm/fault.c:989
el1_abort+0x44/0x64 arch/arm64/kernel/entry-common.c:342
el1h_64_sync_handler+0x50/0xac arch/arm64/kernel/entry-common.c:469
el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:585
do_copy_page kernel/power/snapshot.c:1436 [inline] (P)
safe_copy_page kernel/power/snapshot.c:1457 [inline] (P)
copy_data_page kernel/power/snapshot.c:1508 [inline] (P)
copy_data_pages kernel/power/snapshot.c:1543 [inline] (P)
swsusp_save+0x2d4/0x5a0 kernel/power/snapshot.c:2133 (P)
swsusp_arch_suspend+0x74/0x618 arch/arm64/kernel/hibernate.c:357
create_image kernel/power/hibernate.c:358 [inline]
hibernation_snapshot+0x218/0x43c kernel/power/hibernate.c:442
hibernate+0x1cc/0x3c0 kernel/power/hibernate.c:813
state_store+0xe8/0xf4 kernel/power/main.c:821
kobj_attr_store+0x18/0x34 lib/kobject.c:842
sysfs_kf_write+0x7c/0x98 fs/sysfs/file.c:145
kernfs_fop_write_iter+0x138/0x200 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x244/0x36c fs/read_write.c:687
ksys_write+0x70/0x108 fs/read_write.c:739
__do_sys_write fs/read_write.c:750 [inline]
__se_sys_write fs/read_write.c:747 [inline]
__arm64_sys_write+0x18/0x24 fs/read_write.c:747
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x54/0x10c arch/arm64/kernel/syscall.c:49
el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:121
do_el0_svc+0x1c/0x34 arch/arm64/kernel/syscall.c:140
el0_svc+0x38/0x1fc arch/arm64/kernel/entry-common.c:758
el0t_64_sync_handler+0xa0/0xe4 arch/arm64/kernel/entry-common.c:777
el0t_64_sync+0x1a4/0x1a8 arch/arm64/kernel/entry.S:590
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x43c1c
head: order:2 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x1ffe00000000040(head|node=0|zone=0|lastcpupid=0x7ff|kasantag=0x8)
page_type: f8(unknown)
raw: 01ffe00000000040 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000000f8000000 0000000000000000
head: 01ffe00000000040 0000000000000000 dead000000000122 0000000000000000
head: 0000000000000000 0000000000000000 00000000f8000000 0000000000000000
head: 01ffe00000000002 ffffc1ffc00f0701 00000000ffffffff 00000000ffffffff
head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000004
page dumped because: kasan: bad access detected
Memory state around the buggy address:
fff0000003c1ef00: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
fff0000003c1f000: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
>fff0000003c1f100: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
^
fff0000003c1f200: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
fff0000003c1f300: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
==================================================================
Enabling non-boot CPUs ...
CPU1 is up
PM: Cannot find swap device, try swapon -a
PM: Cannot get swap writer
OOM killer enabled.
Restarting tasks: Starting
Restarting tasks: Done
PM: hibernation: hibernation exit
---
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.
prev parent reply other threads:[~2026-10-09 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 14:04 syzbot
2026-10-09 1:03 ` syzbot [this message]
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=6ac83d60.8cdf6287.1eb53.0040.GAE@google.com \
--to=syzbot+461576769f21a04b4bc0@syzkaller.appspotmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®