linux-kernel - [syzbot] BUG: Bad rss-counter state (6)

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: <6987d9a1.a00a0220.34fa92.0039.GAE@google.com>
Date: Sat, 07 Feb 2026 16:32:33 -0800
From: syzbot <syzbot+5981772e2b70777a3b01@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] BUG: Bad rss-counter state (6)

Hello,

syzbot found the following issue on:

HEAD commit:    e84d960149e7 Merge tag 'for-6.19-rc5-tag' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145c3b9a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1859476832863c41
dashboard link: https://syzkaller.appspot.com/bug?extid=5981772e2b70777a3b01
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-e84d9601.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/da873e352c9a/vmlinux-e84d9601.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee84236e98b6/bzImage-e84d9601.xz

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

BUG: Bad rss-counter state mm:ffff88801b484980 type:MM_FILEPAGES val:1 Comm:syz-executor Pid:32615
BUG: Bad rss-counter state mm:ffff88801b484980 type:MM_SWAPENTS val:148 Comm:syz-executor Pid:32615


---
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 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