[v5.15] kernel BUG in pskb_expand_head (2)
0 views
Skip to first unread message
syzbot
Jul 18, 2025, 10:25:41 AMJul 18
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1132fd8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f7ef907dd63/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9fa50894c6f/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78f74ec5a263/bzImage-c7964837.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+49fbf2...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1703!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1324 Comm: kworker/1:2 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events sk_psock_backlog
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc9000551f8f0 EFLAGS: 00010293
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff8880228d1dc0
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100c16ab0c
R10: ffffed100c16ab0c R11: 1ffff1100c16ab0b R12: 0000000000008080
R13: ffff888060b5585c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000df000 CR3: 00000000721d3000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
__pskb_pull_tail+0xb6/0x1530 net/core/skbuff.c:2257
__skb_linearize include/linux/skbuff.h:3508 [inline]
skb_linearize include/linux/skbuff.h:3520 [inline]
sk_psock_skb_ingress_enqueue+0x67/0x690 net/core/skmsg.c:537
sk_psock_skb_ingress net/core/skmsg.c:581 [inline]
sk_psock_handle_skb net/core/skmsg.c:619 [inline]
sk_psock_backlog+0xaef/0x1330 net/core/skmsg.c:676
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 396f6a5d08f3070a ]---
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc9000551f8f0 EFLAGS: 00010293
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff8880228d1dc0
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100c16ab0c
R10: ffffed100c16ab0c R11: 1ffff1100c16ab0b R12: 0000000000008080
R13: ffff888060b5585c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000df000 CR3: 000000002aabf000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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
syzbot found the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1132fd8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f7ef907dd63/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9fa50894c6f/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78f74ec5a263/bzImage-c7964837.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+49fbf2...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1703!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1324 Comm: kworker/1:2 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events sk_psock_backlog
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc9000551f8f0 EFLAGS: 00010293
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff8880228d1dc0
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100c16ab0c
R10: ffffed100c16ab0c R11: 1ffff1100c16ab0b R12: 0000000000008080
R13: ffff888060b5585c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000df000 CR3: 00000000721d3000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
__pskb_pull_tail+0xb6/0x1530 net/core/skbuff.c:2257
__skb_linearize include/linux/skbuff.h:3508 [inline]
skb_linearize include/linux/skbuff.h:3520 [inline]
sk_psock_skb_ingress_enqueue+0x67/0x690 net/core/skmsg.c:537
sk_psock_skb_ingress net/core/skmsg.c:581 [inline]
sk_psock_handle_skb net/core/skmsg.c:619 [inline]
sk_psock_backlog+0xaef/0x1330 net/core/skmsg.c:676
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 396f6a5d08f3070a ]---
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc9000551f8f0 EFLAGS: 00010293
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff8880228d1dc0
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100c16ab0c
R10: ffffed100c16ab0c R11: 1ffff1100c16ab0b R12: 0000000000008080
R13: ffff888060b5585c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000df000 CR3: 000000002aabf000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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
syzbot
Jul 18, 2025, 11:37:28 AMJul 18
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11cb5d8c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128cb8f0580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f7ef907dd63/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9fa50894c6f/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78f74ec5a263/bzImage-c7964837.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+49fbf2...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1703!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4295 Comm: kworker/0:9 Not tainted 5.15.189-syzkaller #0
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff88807e733b80
R10: ffffed100e9ad26c R11: 1ffff1100e9ad26b R12: 0000000000008080
R13: ffff888074d6935c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff88807e733b80
R10: ffffed100e9ad26c R11: 1ffff1100e9ad26b R12: 0000000000008080
R13: ffff888074d6935c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15cb5d8c580000
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128cb8f0580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f7ef907dd63/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9fa50894c6f/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78f74ec5a263/bzImage-c7964837.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+49fbf2...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1703!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events sk_psock_backlog
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc900031af8f0 EFLAGS: 00010293
Workqueue: events sk_psock_backlog
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff88807e733b80
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100e9ad26c
R10: ffffed100e9ad26c R11: 1ffff1100e9ad26b R12: 0000000000008080
R13: ffff888074d6935c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000283000 CR3: 0000000074dfe000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__pskb_pull_tail+0xb6/0x1530 net/core/skbuff.c:2257
__skb_linearize include/linux/skbuff.h:3508 [inline]
skb_linearize include/linux/skbuff.h:3520 [inline]
sk_psock_skb_ingress_enqueue+0x67/0x690 net/core/skmsg.c:537
sk_psock_skb_ingress net/core/skmsg.c:581 [inline]
sk_psock_handle_skb net/core/skmsg.c:619 [inline]
sk_psock_backlog+0xaef/0x1330 net/core/skmsg.c:676
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace c9910daf832e466d ]---
<TASK>
__pskb_pull_tail+0xb6/0x1530 net/core/skbuff.c:2257
__skb_linearize include/linux/skbuff.h:3508 [inline]
skb_linearize include/linux/skbuff.h:3520 [inline]
sk_psock_skb_ingress_enqueue+0x67/0x690 net/core/skmsg.c:537
sk_psock_skb_ingress net/core/skmsg.c:581 [inline]
sk_psock_handle_skb net/core/skmsg.c:619 [inline]
sk_psock_backlog+0xaef/0x1330 net/core/skmsg.c:676
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
RIP: 0010:pskb_expand_head+0x10c1/0x10f0 net/core/skbuff.c:1703
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RSP: 0018:ffffc900031af8f0 EFLAGS: 00010293
Code: 7d ec f9 e9 32 f4 ff ff e8 7c 1a a8 f9 4c 89 ef 48 c7 c6 20 3c fe 8a e8 3d 85 da f9 0f 0b e8 66 1a a8 f9 0f 0b e8 5f 1a a8 f9 <0f> 0b 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c bf fa ff ff 48 8b
RAX: ffffffff87cfa9c1 RBX: 0000000000000ec0 RCX: ffff88807e733b80
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed100e9ad26c
R10: ffffed100e9ad26c R11: 1ffff1100e9ad26b R12: 0000000000008080
R13: ffff888074d6935c R14: 0000000000000002 R15: 0000000000000a20
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000283000 CR3: 000000002ab1e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
syzbot
Sep 23, 2025, 8:21:05 PM (2 days ago) Sep 23
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 4dba44333a11522df54b49aa1f2edfaf6ce35fc7
Author: Jiayuan Chen <jiayua...@linux.dev>
Date: Mon Apr 7 14:21:22 2025 +0000
bpf, sockmap: Fix panic when calling skb_linearize
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11748f12580000
start commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
#syz fix: bpf, sockmap: Fix panic when calling skb_linearize
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 4dba44333a11522df54b49aa1f2edfaf6ce35fc7
Author: Jiayuan Chen <jiayua...@linux.dev>
Date: Mon Apr 7 14:21:22 2025 +0000
bpf, sockmap: Fix panic when calling skb_linearize
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11748f12580000
start commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
dashboard link: https://syzkaller.appspot.com/bug?extid=49fbf22a9769a1d5038e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15cb5d8c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128cb8f0580000
If the result looks correct, please mark the issue as fixed by replying with:
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128cb8f0580000
#syz fix: bpf, sockmap: Fix panic when calling skb_linearize
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages