From: syzbot <syzbot+ee09ee2112d03c35f1f7@syzkaller.appspotmail.com>
To: joern@lazybastard.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, miquel.raynal@bootlin.com,
richard@nod.at, syzkaller-bugs@googlegroups.com,
vigneshr@ti.com
Subject: [syzbot] [mtd?] BUG: unable to handle kernel paging request in phram_read
Date: Tue, 17 Nov 2026 17:49:39 -0800 [thread overview]
Message-ID: <6afd0433.8f566acc.2517be.000f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: ad3fc05c7e65 arm64: suspend: Only track cpuidle context fo..
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=165de94e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e8e6c1701ad8af2
dashboard link: https://syzkaller.appspot.com/bug?extid=ee09ee2112d03c35f1f7
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1796373d580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13fbe5c3580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a30beb3b2b82/disk-ad3fc05c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2eaac3d8da90/vmlinux-ad3fc05c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/212a161a069b/Image-ad3fc05c.gz.xz
The issue was bisected by AI to candidate commits (most relevant first):
1da177e4c3f4 Linux-2.6.12-rc2
f3d45ac21e46 mtd: phram: Module parameters add writable permissions
285133040e6c arm64: Import latest memcpy()/memmove() implementation
AI reasoning: https://syzkaller.appspot.com/ai_job?id=c053ce4a-8b95-428d-87ad-63a0065b8ed9
AI-generated root cause summary:
In drivers/mtd/devices/phram.c, registering a phram device via module parameter
or sysfs (/sys/module/phram/parameters/phram) invokes register_device() with
pdev = NULL, which causes new->cached to be false. As a result, phram_map() maps
the physical memory region using ioremap() (mapped as PROT_DEVICE_nGnRE on
arm64) and forces the pointer into mtd->priv, yet phram_read(), phram_write(),
and phram_erase() access it using standard memcpy() and memset() instead of I/O
memory accessors (like memcpy_fromio()). When scanning partition headers (e.g.,
ftl_add_mtd() reading a 68-byte header via mtd_read()), arm64's memcpy
implementation issues pair-load (ldp) instructions at unaligned offsets, which
unconditionally triggers an alignment fault (FSC = 0x21) on Device memory and
crashes the kernel.
full analysis: https://syzkaller.appspot.com/x/ai_root_cause?x=ee09ee2112d03c35f1f7
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ee09ee2112d03c35f1f7@syzkaller.appspotmail.com
Unable to handle kernel paging request at virtual address ffff800090ffe024
KASAN: probably user-memory-access in range [0x0000000487ff0120-0x0000000487ff0127]
Mem abort info:
ESR = 0x0000000096000021
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x21: alignment fault
Data abort info:
ISV = 0, ISS = 0x00000021, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0
swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000002193b5000
[ffff800090ffe024] pgd=0000000000000000, p4d=100000021f6f0003, pud=100000021f6f1003, pmd=10000001013e1403, pte=0068000000000713
Internal error: Oops: 0000000096000021 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 4957 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
pstate: 23400005 (nzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __pi_memcpy_generic+0x98/0x22c arch/arm64/lib/memcpy.S:114
lr : __asan_memcpy+0x68/0x84 mm/kasan/shadow.c:109
sp : ffff800095836fc0
x29: ffff800095836fc0 x28: 1fffe00019f6102f x27: ffff0000cfb08000
x26: dfff800000000000 x25: ffff800095837150 x24: dfff800000000000
x23: ffff0000cfb08190 x22: ffff800082ab0064 x21: ffff800095837370
x20: ffff800090ffe000 x19: 0000000000000044 x18: 1fffe000359cf228
x17: 4a414d0064746d3d x16: 4d45545359534255 x15: ffff800080d0603c
x14: 0000000000000001 x13: 0000000000000009 x12: 0000000000000004
x11: ffff700012b06e76 x10: ffff700012b06e76 x9 : ffffffffffffffff
x8 : ffffffffffffffff x7 : ffffffffffffffff x6 : ffffffff14000400
x5 : ffff8000958373b4 x4 : ffff800090ffe044 x3 : ffff800082ab0064
x2 : 0000000000000044 x1 : ffff800090ffe000 x0 : ffff800095837370
Call trace:
__pi_memcpy_generic+0x98/0x22c arch/arm64/lib/memcpy.S:113 (P)
phram_read+0x64/0x98 drivers/mtd/devices/phram.c:70
mtd_read_oob_std+0x180/0x19c drivers/mtd/mtdcore.c:1702
mtd_read_oob+0x1fc/0x4ec drivers/mtd/mtdcore.c:1811
mtd_read+0xd0/0x1a8 drivers/mtd/mtdcore.c:1603
scan_header drivers/mtd/ftl.c:164 [inline]
ftl_add_mtd+0x1e8/0x16d8 drivers/mtd/ftl.c:1017
blktrans_notify_add+0xa8/0xf8 drivers/mtd/mtd_blkdevs.c:469
add_mtd_device+0xedc/0x1504 drivers/mtd/mtdcore.c:828
mtd_device_parse_register+0x660/0x7a0 drivers/mtd/mtdcore.c:1156
register_device+0x340/0x51c drivers/mtd/devices/phram.c:162
phram_setup+0x354/0x4fc drivers/mtd/devices/phram.c:324
phram_param_call+0x34/0x90 drivers/mtd/devices/phram.c:349
param_attr_store+0x144/0x1bc kernel/params.c:591
module_attr_store+0x6c/0x94 kernel/params.c:906
sysfs_kf_write+0xe0/0x108 fs/sysfs/file.c:145
kernfs_fop_write_iter+0x260/0x3b8 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x51c/0xa0c fs/read_write.c:687
ksys_write+0x12c/0x228 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+0x84/0x98 fs/read_write.c:747
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:797
el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:816
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606
Code: d65f03c0 d503201f a9401c26 a9412428 (a97e2c8a)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d65f03c0 ret
4: d503201f nop
8: a9401c26 ldp x6, x7, [x1]
c: a9412428 ldp x8, x9, [x1, #16]
* 10: a97e2c8a ldp x10, x11, [x4, #-32] <-- 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.
For information about AI bisection see: https://goo.gl/tpsmEJ#ai-bisection
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
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+ee09ee2112d03c35f1f7@syzkaller.appspotmail.com>
To: joern@lazybastard.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, miquel.raynal@bootlin.com,
richard@nod.at, syzkaller-bugs@googlegroups.com,
vigneshr@ti.com
Subject: [syzbot] [mtd?] BUG: unable to handle kernel paging request in phram_read
Date: Tue, 17 Nov 2026 17:49:39 -0800 [thread overview]
Message-ID: <6afd0433.8f566acc.2517be.000f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: ad3fc05c7e65 arm64: suspend: Only track cpuidle context fo..
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=165de94e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e8e6c1701ad8af2
dashboard link: https://syzkaller.appspot.com/bug?extid=ee09ee2112d03c35f1f7
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1796373d580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13fbe5c3580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a30beb3b2b82/disk-ad3fc05c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2eaac3d8da90/vmlinux-ad3fc05c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/212a161a069b/Image-ad3fc05c.gz.xz
The issue was bisected by AI to candidate commits (most relevant first):
1da177e4c3f4 Linux-2.6.12-rc2
f3d45ac21e46 mtd: phram: Module parameters add writable permissions
285133040e6c arm64: Import latest memcpy()/memmove() implementation
AI reasoning: https://syzkaller.appspot.com/ai_job?id=c053ce4a-8b95-428d-87ad-63a0065b8ed9
AI-generated root cause summary:
In drivers/mtd/devices/phram.c, registering a phram device via module parameter
or sysfs (/sys/module/phram/parameters/phram) invokes register_device() with
pdev = NULL, which causes new->cached to be false. As a result, phram_map() maps
the physical memory region using ioremap() (mapped as PROT_DEVICE_nGnRE on
arm64) and forces the pointer into mtd->priv, yet phram_read(), phram_write(),
and phram_erase() access it using standard memcpy() and memset() instead of I/O
memory accessors (like memcpy_fromio()). When scanning partition headers (e.g.,
ftl_add_mtd() reading a 68-byte header via mtd_read()), arm64's memcpy
implementation issues pair-load (ldp) instructions at unaligned offsets, which
unconditionally triggers an alignment fault (FSC = 0x21) on Device memory and
crashes the kernel.
full analysis: https://syzkaller.appspot.com/x/ai_root_cause?x=ee09ee2112d03c35f1f7
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ee09ee2112d03c35f1f7@syzkaller.appspotmail.com
Unable to handle kernel paging request at virtual address ffff800090ffe024
KASAN: probably user-memory-access in range [0x0000000487ff0120-0x0000000487ff0127]
Mem abort info:
ESR = 0x0000000096000021
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x21: alignment fault
Data abort info:
ISV = 0, ISS = 0x00000021, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0
swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000002193b5000
[ffff800090ffe024] pgd=0000000000000000, p4d=100000021f6f0003, pud=100000021f6f1003, pmd=10000001013e1403, pte=0068000000000713
Internal error: Oops: 0000000096000021 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 4957 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
pstate: 23400005 (nzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __pi_memcpy_generic+0x98/0x22c arch/arm64/lib/memcpy.S:114
lr : __asan_memcpy+0x68/0x84 mm/kasan/shadow.c:109
sp : ffff800095836fc0
x29: ffff800095836fc0 x28: 1fffe00019f6102f x27: ffff0000cfb08000
x26: dfff800000000000 x25: ffff800095837150 x24: dfff800000000000
x23: ffff0000cfb08190 x22: ffff800082ab0064 x21: ffff800095837370
x20: ffff800090ffe000 x19: 0000000000000044 x18: 1fffe000359cf228
x17: 4a414d0064746d3d x16: 4d45545359534255 x15: ffff800080d0603c
x14: 0000000000000001 x13: 0000000000000009 x12: 0000000000000004
x11: ffff700012b06e76 x10: ffff700012b06e76 x9 : ffffffffffffffff
x8 : ffffffffffffffff x7 : ffffffffffffffff x6 : ffffffff14000400
x5 : ffff8000958373b4 x4 : ffff800090ffe044 x3 : ffff800082ab0064
x2 : 0000000000000044 x1 : ffff800090ffe000 x0 : ffff800095837370
Call trace:
__pi_memcpy_generic+0x98/0x22c arch/arm64/lib/memcpy.S:113 (P)
phram_read+0x64/0x98 drivers/mtd/devices/phram.c:70
mtd_read_oob_std+0x180/0x19c drivers/mtd/mtdcore.c:1702
mtd_read_oob+0x1fc/0x4ec drivers/mtd/mtdcore.c:1811
mtd_read+0xd0/0x1a8 drivers/mtd/mtdcore.c:1603
scan_header drivers/mtd/ftl.c:164 [inline]
ftl_add_mtd+0x1e8/0x16d8 drivers/mtd/ftl.c:1017
blktrans_notify_add+0xa8/0xf8 drivers/mtd/mtd_blkdevs.c:469
add_mtd_device+0xedc/0x1504 drivers/mtd/mtdcore.c:828
mtd_device_parse_register+0x660/0x7a0 drivers/mtd/mtdcore.c:1156
register_device+0x340/0x51c drivers/mtd/devices/phram.c:162
phram_setup+0x354/0x4fc drivers/mtd/devices/phram.c:324
phram_param_call+0x34/0x90 drivers/mtd/devices/phram.c:349
param_attr_store+0x144/0x1bc kernel/params.c:591
module_attr_store+0x6c/0x94 kernel/params.c:906
sysfs_kf_write+0xe0/0x108 fs/sysfs/file.c:145
kernfs_fop_write_iter+0x260/0x3b8 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x51c/0xa0c fs/read_write.c:687
ksys_write+0x12c/0x228 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+0x84/0x98 fs/read_write.c:747
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:797
el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:816
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606
Code: d65f03c0 d503201f a9401c26 a9412428 (a97e2c8a)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d65f03c0 ret
4: d503201f nop
8: a9401c26 ldp x6, x7, [x1]
c: a9412428 ldp x8, x9, [x1, #16]
* 10: a97e2c8a ldp x10, x11, [x4, #-32] <-- 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.
For information about AI bisection see: https://goo.gl/tpsmEJ#ai-bisection
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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2026-11-18 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 1:49 syzbot [this message]
2026-11-18 1:49 ` [syzbot] [mtd?] BUG: unable to handle kernel paging request in phram_read syzbot
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=6afd0433.8f566acc.2517be.000f.GAE@google.com \
--to=syzbot+ee09ee2112d03c35f1f7@syzkaller.appspotmail.com \
--cc=joern@lazybastard.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vigneshr@ti.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.