CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust
In the Linux kernel, the following vulnerability has been resolved:
ipv4: ip_gre: make ipgre_header() robust
Analog to commit db5b4e39c4e6 ("ip6_gre: make ip6gre_header() robust")
Over the years, syzbot found many ways to crash the kernel
in ipgre_header() [1].
This involves team or bonding drivers ability to dynamically
change their dev->needed_headroom and/or dev->hard_header_len
In this particular crash mld_newpack() allocated an skb
with a too small reserve/headroom, and by the time mld_sendpack()
was called, syzbot managed to attach an ipgre device.
[1]
skbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0
kernel BUG at net/core/skbuff.c:213 !
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: mld mld_ifc_work
RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213
Call Trace:
<TASK>
skb_under_panic net/core/skbuff.c:223 [inline]
skb_push+0xc3/0xe0 net/core/skbuff.c:2641
ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897
dev_hard_header include/linux/netdevice.h:3436 [inline]
neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618
NF_HOOK_COND include/linux/netfilter.h:307 [inline]
ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247
NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318
mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855
mld_send_cr net/ipv6/mcast.c:2154 [inline]
mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693
process_one_work kernel/workqueue.c:3257 [inline]
process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
Security readout for executives and security teams
Plain-English summary
A Linux networking flaw can crash the kernel when GRE tunneling is combined with dynamically changing team or bonding interfaces. A crash could interrupt services or reboot a host. The supplied evidence does not establish remote reachability, required privileges, or data compromise.
Executive priority
Prioritize assessment and patching for network appliances, virtualization hosts, and critical Linux servers using these interface combinations. Treat this as an availability risk requiring timely remediation, but the supplied evidence does not justify an emergency, enterprise-wide response based on active exploitation.
Technical view
A packet buffer can be allocated with insufficient headroom before an IP GRE device changes interface header requirements. ipgre_header() may then push beyond the reserved buffer, triggering skb_under_panic and a kernel BUG.
Likely exposure
Potential exposure is limited to affected Linux kernels where IP GRE and dynamically changing team or bonding interfaces are used. The supplied version data is ambiguous, so distribution-specific kernel packages and backports require vendor confirmation.
Exploitation context
The crash was produced by syzbot under a constructed interface-change condition. The bundle reports no KEV listing and provides no evidence of active exploitation. It does not establish whether an unprivileged or remote attacker can trigger the flaw.
Researcher notes
The record provides a concrete kernel panic trace and multiple stable-tree fixes, but no CVSS, CWE, validated attack vector, privilege requirement, or reliable package-level affected matrix. The repeated commit hashes and mixed version entries should not be interpreted as definitive distribution exposure.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable upstream stable fix or backport.
Reboot affected hosts after updating and confirm the patched kernel is running.
If patching is delayed, consult vendor guidance before changing GRE, team, or bonding configurations.
Validation and detection
Inventory running kernel versions and systems using IP GRE, team, or bonding interfaces.
Confirm each kernel package contains the applicable fix through vendor advisories or changelogs.
Check kernel logs for skb_under_panic, ipgre_header, or related kernel BUG events.
Verify updated hosts booted into the intended patched kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23011 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.