[syzbot] WARNING in ring_buffer_read_page

Hello,

syzbot found the following issue on:

HEAD commit:    f9a2394a2348 Merge tag 'mm-hotfixes-stable-2026-08-06-18-4..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12920fb9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=54b05b209062aef2
dashboard link: https://syzkaller.appspot.com/bug?extid=b68a3375cf039ac37051
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13a1c132580000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
1
WARNING: kernel/trace/ring_buffer.c:5957 at __rb_get_reader_page+0xe70/0x1450 kernel/trace/ring_buffer.c:5957, CPU#1: syz-executor422/6023
Modules linked in:
CPU: 1 UID: 0 PID: 6023 Comm: syz-executor422 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__rb_get_reader_page+0xe70/0x1450 kernel/trace/ring_buffer.c:5957
Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 12 04 00 00 48 8b 43 10 be 04 00 00 00 48 8d 68 08 48 89 ef e8 75 ea 6b 00 f0 ff 45 00 90 <0f> 0b 90 e9 1c f9 ff ff 4c 8b 74 24 60 e8 1e 65 fc ff 48 8b 54 24
RSP: 0018:ffffc9000370fa20 EFLAGS: 00010006
RAX: 0000000000000001 RBX: ffff88801cade000 RCX: ffffffff820c7a2b
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffff88813fe62008
RBP: ffff88813fe62008 R08: 0000000000000001 R09: ffffed1027fcc401
R10: ffff88813fe6200b R11: ffff88801cade0a8 R12: ffff88801f75d980
R13: ffffed1003eebb32 R14: 0000000000000ff0 R15: ffff88801f75d990
FS:  00007effc71086c0(0000) GS:ffff888123fe4000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007effc7106000 CR3: 0000000076748000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 rb_get_reader_page kernel/trace/ring_buffer.c:5981 [inline]
 ring_buffer_read_page+0x8ed/0x1710 kernel/trace/ring_buffer.c:7103
 tracing_buffers_read+0x2bf/0xaf0 kernel/trace/trace.c:7125
 vfs_read+0x1e4/0xb40 fs/read_write.c:572
 ksys_read+0x12a/0x250 fs/read_write.c:716
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x10b/0x830 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7effc8166cde
Code: 08 0f 85 f5 e2 ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 90 41 57 41 56 4d 89 c6 41 55 4d 89 cd 41 54 55 53 48 83 ec 08
RSP: 002b:00007effc7104198 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007effc71086c0 RCX: 00007effc8166cde
RDX: 0000000000004000 RSI: 00007effc7104200 RDI: 0000000000000006
RBP: 00007effc7104200 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007effc81e0b20
R13: 0000000000000000 R14: 00007ffdeadf5850 R15: 00007ffdeadf5938
 </TASK>


---
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 [email protected].

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