[v6.1] BUG: unable to handle kernel paging request in e1000_get_cfg_done_82571

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14886cc6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=2b55fb78e177efdc9be9
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz

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

e1000e 0000:00:03.0: The NVM Checksum Is Not Valid
BUG: unable to handle page fault for address: ffffc900045ae010
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 17400067 P4D 17400067 PUD 17622067 PMD 24b49067 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4346 Comm: kworker/0:6 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events work_for_cpu_fn
RIP: 0010:readl arch/x86/include/asm/io.h:61 [inline]
RIP: 0010:__er32 drivers/net/ethernet/intel/e1000e/e1000.h:579 [inline]
RIP: 0010:e1000_get_cfg_done_82571+0x3e/0x100 drivers/net/ethernet/intel/e1000e/82571.c:851
Code: fc ff df e8 24 c0 e1 fb 4c 8d 73 08 bd 9d ff ff ff 4d 89 f4 49 c1 ec 03 43 80 3c 3c 00 74 08 4c 89 f7 e8 c5 ec 32 fc 49 8b 06 <44> 8b a8 10 10 00 00 44 89 ee 81 e6 00 00 04 00 31 ff e8 4b c3 e1
RSP: 0018:ffffc90003f97a48 EFLAGS: 00010246
RAX: ffffc900045ad000 RBX: ffff88807b5e92f8 RCX: ffff888026d79e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88807b5e92f8
RBP: 00000000ffffff9d R08: ffffffff90b1028f R09: 1ffffffff2162051
R10: dffffc0000000000 R11: fffffbfff2162052 R12: 1ffff1100f6bd260
R13: ffff88807b5e8c80 R14: ffff88807b5e9300 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc900045ae010 CR3: 00000000183af000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
e1000_phy_hw_reset drivers/net/ethernet/intel/e1000e/e1000.h:517 [inline]
e1000_probe+0x1f58/0x29f0 drivers/net/ethernet/intel/e1000e/netdev.c:7701
local_pci_probe+0xc5/0x150 drivers/pci/pci-driver.c:324
work_for_cpu_fn+0x50/0x80 kernel/workqueue.c:5184
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
process_scheduled_works kernel/workqueue.c:2355 [inline]
worker_thread+0xdd1/0x12a0 kernel/workqueue.c:2444
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Modules linked in:
Dumping ftrace buffer:
(ftrace buffer empty)
CR2: ffffc900045ae010
---[ end trace 0000000000000000 ]---
RSP: 0018:ffffc90003f97a48 EFLAGS: 00010246
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CR2: ffffc900045ae010 CR3: 00000000183af000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: fc cld
1: ff lcall (bad)
2: df e8 fucomip %st(0),%st
4: 24 c0 and $0xc0,%al
6: e1 fb loope 0x3
8: 4c 8d 73 08 lea 0x8(%rbx),%r14
c: bd 9d ff ff ff mov $0xffffff9d,%ebp
11: 4d 89 f4 mov %r14,%r12
14: 49 c1 ec 03 shr $0x3,%r12
18: 43 80 3c 3c 00 cmpb $0x0,(%r12,%r15,1)
1d: 74 08 je 0x27
1f: 4c 89 f7 mov %r14,%rdi
22: e8 c5 ec 32 fc call 0xfc32ecec
27: 49 8b 06 mov (%r14),%rax
* 2a: 44 8b a8 10 10 00 00 mov 0x1010(%rax),%r13d <-- trapping instruction
31: 44 89 ee mov %r13d,%esi
34: 81 e6 00 00 04 00 and $0x40000,%esi
3a: 31 ff xor %edi,%edi
3c: e8 .byte 0xe8
3d: 4b c3 rex.WXB ret
3f: e1 .byte 0xe1


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