[kernel?] KASAN: stack-out-of-bounds Read in __remove_hrtimer

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cec24b8b6bb8 Merge tag 'char-misc-6.4-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=116b1778280000
kernel config: https://syzkaller.appspot.com/x/.config?x=cd501cbfafae3e42
dashboard link: https://syzkaller.appspot.com/bug?extid=84233b4e936dd2dc50ba
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org tg...@linutronix.de]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1f9801b1d3f8/disk-cec24b8b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7fcfb71cf6a0/vmlinux-cec24b8b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb4ad0d7751c/bzImage-cec24b8b.xz

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

==================================================================
BUG: KASAN: stack-out-of-bounds in __remove_hrtimer+0x250/0x2a0 kernel/time/hrtimer.c:1109
Read of size 1 at addr ffffc90003d2fdd0 by task syz-executor.1/14332

CPU: 0 PID: 14332 Comm: syz-executor.1 Not tainted 6.3.0-syzkaller-09882-gcec24b8b6bb8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:319
print_report mm/kasan/report.c:430 [inline]
kasan_report+0x11c/0x130 mm/kasan/report.c:536
__remove_hrtimer+0x250/0x2a0 kernel/time/hrtimer.c:1109
__run_hrtimer kernel/time/hrtimer.c:1665 [inline]
__hrtimer_run_queues+0x4e0/0xbe0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x320/0x7b0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x14a/0x430 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x92/0xc0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:645
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x70 kernel/kcov.c:200
Code: e6 9a 8c 02 66 0f 1f 44 00 00 f3 0f 1e fa 48 8b be a8 01 00 00 e8 b0 ff ff ff 31 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 <f3> 0f 1e fa 65 8b 05 9d f9 7f 7e 89 c1 48 8b 34 24 81 e1 00 01 00
RSP: 0018:ffffc9001492f780 EFLAGS: 00000216
RAX: 00000000000115f6 RBX: 0000000000000200 RCX: ffffc90005dba000
RDX: 0000000000040000 RSI: ffffffff8167ca95 RDI: 0000000000000007
RBP: ffffffff8d259158 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000200 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff8d259100 R14: dffffc0000000000 R15: 0000000000000001
console_emit_next_record arch/x86/include/asm/irqflags.h:42 [inline]
console_flush_all+0x61b/0xcc0 kernel/printk/printk.c:2931
console_unlock+0xb8/0x1f0 kernel/printk/printk.c:3005
vprintk_emit+0x1bd/0x600 kernel/printk/printk.c:2305
vprintk+0x84/0xa0 kernel/printk/printk_safe.c:50
_printk+0xbf/0xf0 kernel/printk/printk.c:2326
reiserfs_info+0xe1/0x140 fs/reiserfs/prints.c:303
create_privroot fs/reiserfs/xattr.c:900 [inline]
reiserfs_xattr_init+0x612/0xbc0 fs/reiserfs/xattr.c:1006
reiserfs_remount+0xb62/0x1650 fs/reiserfs/super.c:1586
legacy_reconfigure+0x119/0x180 fs/fs_context.c:633
reconfigure_super+0x40c/0xa30 fs/super.c:956
do_remount fs/namespace.c:2701 [inline]
path_mount+0x1846/0x1e40 fs/namespace.c:3361
do_mount fs/namespace.c:3382 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x283/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f1c6fa8d69a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1c70709f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1c6fa8d69a
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 0000000000000000
RBP: 00007f1c7070a020 R08: 00007f1c7070a020 R09: 0000000001a484bc
R10: 0000000001a484bc R11: 0000000000000202 R12: 00000000200000c0
R13: 0000000020000100 R14: 00007f1c70709fe0 R15: 0000000020003d00
</TASK>

The buggy address belongs to the virtual mapping at
[ffffc90003d28000, ffffc90003d31000) created by:
kernel_clone+0xeb/0x890 kernel/fork.c:2774

The buggy address belongs to the physical page:
page:ffffea0001011a80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x4046a
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x2dc2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), pid 5020, tgid 5020 (syz-executor.1), ts 188356908312, free_ts 9559644638
prep_new_page mm/page_alloc.c:2553 [inline]
get_page_from_freelist+0x1190/0x2e20 mm/page_alloc.c:4326
__alloc_pages+0x1cb/0x4a0 mm/page_alloc.c:5592
alloc_pages+0x1aa/0x270 mm/mempolicy.c:2277
vm_area_alloc_pages mm/vmalloc.c:2957 [inline]
__vmalloc_area_node mm/vmalloc.c:3033 [inline]
__vmalloc_node_range+0xb1c/0x14a0 mm/vmalloc.c:3205
alloc_thread_stack_node kernel/fork.c:311 [inline]
dup_task_struct kernel/fork.c:982 [inline]
copy_process+0x134c/0x7580 kernel/fork.c:2190
kernel_clone+0xeb/0x890 kernel/fork.c:2774
__do_sys_clone+0xba/0x100 kernel/fork.c:2917
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1454 [inline]
free_pcp_prepare+0x5d5/0xa50 mm/page_alloc.c:1504
free_unref_page_prepare mm/page_alloc.c:3388 [inline]
free_unref_page+0x1d/0x490 mm/page_alloc.c:3483
free_contig_range+0xb5/0x180 mm/page_alloc.c:9551
destroy_args+0x6c4/0x920 mm/debug_vm_pgtable.c:1023
debug_vm_pgtable+0x242a/0x4640 mm/debug_vm_pgtable.c:1403
do_one_initcall+0x102/0x540 init/main.c:1313
do_initcall_level init/main.c:1386 [inline]
do_initcalls init/main.c:1402 [inline]
do_basic_setup init/main.c:1421 [inline]
kernel_init_freeable+0x696/0xc00 init/main.c:1641
kernel_init+0x1e/0x2c0 init/main.c:1529
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

Memory state around the buggy address:
ffffc90003d2fc80: f3 f3 f3 00 f1 f1 f1 00 00 f2 f2 00 00 00 f3 f3
ffffc90003d2fd00: f3 f3 f3 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00
>ffffc90003d2fd80: f3 f3 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00
^
ffffc90003d2fe00: f3 f3 00 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3
ffffc90003d2fe80: f3 00 00 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3
==================================================================
----------------
Code disassembly (best guess):
0: e6 9a out %al,$0x9a
2: 8c 02 mov %es,(%rdx)
4: 66 0f 1f 44 00 00 nopw 0x0(%rax,%rax,1)
a: f3 0f 1e fa endbr64
e: 48 8b be a8 01 00 00 mov 0x1a8(%rsi),%rdi
15: e8 b0 ff ff ff callq 0xffffffca
1a: 31 c0 xor %eax,%eax
1c: c3 retq
1d: 66 66 2e 0f 1f 84 00 data16 nopw %cs:0x0(%rax,%rax,1)
24: 00 00 00 00
28: 66 90 xchg %ax,%ax
* 2a: f3 0f 1e fa endbr64 <-- trapping instruction
2e: 65 8b 05 9d f9 7f 7e mov %gs:0x7e7ff99d(%rip),%eax # 0x7e7ff9d2
35: 89 c1 mov %eax,%ecx
37: 48 8b 34 24 mov (%rsp),%rsi
3b: 81 .byte 0x81
3c: e1 00 loope 0x3e
3e: 01 00 add %eax,(%rax)


---
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 syzk...@googlegroups.com.

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

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

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

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

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.