The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+d29af9ef5c96a3f5e96c@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@kernel.org,
	herbert@gondor.apana.org.au,  horms@kernel.org,
	ipsec@lists.linux.dev, kuba@kernel.org,
	 linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com,  steffen.klassert@secunet.com,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] WARNING in xfrmi_xmit
Date: Wed, 18 Nov 2026 08:14:57 -0800	[thread overview]
Message-ID: <6afdcf01.ca6cd63e.174a34.0001.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    666539eecdf4 Merge tag 'assoc-array-fixes-v2'
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=170dce4d580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3cc6a7ee2d24d208
dashboard link: https://syzkaller.appspot.com/bug?extid=d29af9ef5c96a3f5e96c
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=105b5755580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10136803580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-666539ee.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57b04345f38e/vmlinux-666539ee.xz
kernel image: https://storage.googleapis.com/syzbot-assets/127bf2b14452/bzImage-666539ee.xz

AI-generated root cause summary:
In AF_XDP generic transmit, xsk_build_skb() and xsk_build_skb_zerocopy()
allocate an sk_buff and advance skb->data using skb_reserve(skb, hr) without
subsequently resetting the network header via skb_reset_network_header().
Because skb->network_header remains 0 (relative to skb->head),
skb_network_offset(skb) returns a negative value equal to -hr (e.g. -64). When
transmitting over devices whose ndo_start_xmit checks pskb_inet_may_pull() (such
as xfrm interfaces), this negative offset is converted to a large unsigned
integer when added to the network header length (0xffffffc0 > INT_MAX),
triggering a DEBUG_NET_WARN_ON_ONCE assertion in pskb_may_pull_reason().

full analysis:  https://syzkaller.appspot.com/x/ai_root_cause?x=d29af9ef5c96a3f5e96c

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

------------[ cut here ]------------
len > ((int)(~0U >> 1))
WARNING: ./include/linux/skbuff.h:2856 at pskb_may_pull_reason include/linux/skbuff.h:2856 [inline], CPU#0: syz.0.17/5560
WARNING: ./include/linux/skbuff.h:2856 at pskb_network_may_pull_reason include/linux/skbuff.h:3286 [inline], CPU#0: syz.0.17/5560
WARNING: ./include/linux/skbuff.h:2856 at pskb_inet_may_pull_reason include/net/ip_tunnels.h:483 [inline], CPU#0: syz.0.17/5560
WARNING: ./include/linux/skbuff.h:2856 at pskb_inet_may_pull include/net/ip_tunnels.h:488 [inline], CPU#0: syz.0.17/5560
WARNING: ./include/linux/skbuff.h:2856 at xfrmi_xmit+0x1844/0x1eb0 net/xfrm/xfrm_interface_core.c:534, CPU#0: syz.0.17/5560
Modules linked in:
CPU: 0 UID: 0 PID: 5560 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:pskb_may_pull_reason include/linux/skbuff.h:2856 [inline]
RIP: 0010:pskb_network_may_pull_reason include/linux/skbuff.h:3286 [inline]
RIP: 0010:pskb_inet_may_pull_reason include/net/ip_tunnels.h:483 [inline]
RIP: 0010:pskb_inet_may_pull include/net/ip_tunnels.h:488 [inline]
RIP: 0010:xfrmi_xmit+0x1844/0x1eb0 net/xfrm/xfrm_interface_core.c:534
Code: db e9 ef fd ff ff e8 bb 47 23 f7 49 8d b4 24 20 01 00 00 48 c7 c7 80 9b 54 8d e8 77 d2 81 f6 e9 c8 f8 ff ff e8 9d 47 23 f7 90 <0f> 0b 90 e9 38 ea ff ff 89 df 44 89 ee e8 9a 49 23 f7 44 39 eb 0f
RSP: 0018:ffffc90001be7300 EFLAGS: 00010293
RAX: ffffffff8aa5f033 RBX: 00000000ffffffc0 RCX: ffff88803050a580
RDX: 0000000000000000 RSI: 00000000ffffffc0 RDI: 0000000000000000
RBP: ffffc90001be7490 R08: ffffc90001be7417 R09: 0000000000000000
R10: ffffc90001be73c0 R11: fffff5200037ce83 R12: 0000000000000000
R13: 1ffff9200037ce74 R14: ffff8880136f5358 R15: ffff8880136f5280
FS:  00005555787d1500(0000) GS:ffff88808a9f1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001f9fc000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 __netdev_start_xmit include/linux/netdevice.h:5457 [inline]
 netdev_start_xmit include/linux/netdevice.h:5466 [inline]
 __dev_direct_xmit+0x4b6/0x730 net/core/dev.c:5164
 __xsk_generic_xmit net/xdp/xsk.c:1288 [inline]
 xsk_generic_xmit+0x27d8/0x47a0 net/xdp/xsk.c:1344
 xsk_poll+0x326/0x670 net/xdp/xsk.c:1472
 sock_poll+0x341/0x460 net/socket.c:1517
 vfs_poll include/linux/poll.h:82 [inline]
 do_pollfd fs/select.c:877 [inline]
 do_poll fs/select.c:920 [inline]
 do_sys_poll+0x98f/0x1150 fs/select.c:1015
 __do_sys_ppoll fs/select.c:1112 [inline]
 __se_sys_ppoll+0x209/0x2b0 fs/select.c:1092
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x171/0x540 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa010ba94d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff5b713048 EFLAGS: 00000246 ORIG_RAX: 000000000000010f
RAX: ffffffffffffffda RBX: 00007fa010e25fa0 RCX: 00007fa010ba94d9
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000200000000800
RBP: 00007fa010c38136 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa010e25fac R14: 00007fa010e25fa0 R15: 00007fa010e25fa0
 </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 syzkaller@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

                 reply	other threads:[~2026-11-18 16:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6afdcf01.ca6cd63e.174a34.0001.GAE@google.com \
    --to=syzbot+d29af9ef5c96a3f5e96c@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=ipsec@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox