CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0.
In the Linux kernel, the following vulnerability has been resolved:
gue: Fix skb memleak with inner IP protocol 0.
syzbot reported skb memleak below. [0]
The repro generated a GUE packet with its inner protocol 0.
gue_udp_recv() returns -guehdr->proto_ctype for "resubmit"
in ip_protocol_deliver_rcu(), but this only works with
non-zero protocol number.
Let's drop such packets.
Note that 0 is a valid number (IPv6 Hop-by-Hop Option).
I think it is not practical to encap HOPOPT in GUE, so once
someone starts to complain, we could pass down a resubmit
flag pointer to distinguish two zeros from the upper layer:
* no error
* resubmit HOPOPT
[0]
BUG: memory leak
unreferenced object 0xffff888109695a00 (size 240):
comm "syz.0.17", pid 6088, jiffies 4294943096
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 40 c2 10 81 88 ff ff 00 00 00 00 00 00 00 00 .@..............
backtrace (crc a84b336f):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
kmem_cache_alloc_noprof+0x3b4/0x590 mm/slub.c:5270
__build_skb+0x23/0x60 net/core/skbuff.c:474
build_skb+0x20/0x190 net/core/skbuff.c:490
__tun_build_skb drivers/net/tun.c:1541 [inline]
tun_build_skb+0x4a1/0xa40 drivers/net/tun.c:1636
tun_get_user+0xc12/0x2030 drivers/net/tun.c:1770
tun_chr_write_iter+0x71/0x120 drivers/net/tun.c:1999
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x45d/0x710 fs/read_write.c:686
ksys_write+0xa7/0x170 fs/read_write.c:738
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Security readout for executives and security teams
Plain-English summary
A specially formed GUE network packet can cause an affected Linux kernel to retain packet memory instead of releasing it. Repeated traffic could consume memory and disrupt system availability. The supplied assessment rates this high at CVSS 7.5, with no confidentiality or integrity impact identified.
Executive priority
Treat this as a high-priority availability issue for exposed GUE infrastructure, especially critical gateways and hosts. Patch promptly after normal compatibility testing. Systems without reachable GUE processing can follow a risk-based maintenance schedule once exposure is verified.
Technical view
The GUE receive path returned a zero inner protocol as a resubmission value, although resubmission requires a non-zero protocol number. This left the socket buffer unfreed. The kernel fix drops GUE packets whose inner protocol is zero, preventing the leak.
Likely exposure
Exposure is most plausible on Linux systems that receive GUE traffic from untrusted networks. Systems not processing GUE have lower practical risk. The bundle identifies multiple stable kernel lines but does not clearly provide complete introduced-through-fixed version ranges, so verify vendor backports by build.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Discovery came from syzbot with a reproducer. The supplied CVSS vector describes network-reachable, low-complexity, unauthenticated exploitation affecting availability only.
Researcher notes
Protocol value zero is valid for IPv6 Hop-by-Hop Options, but the patch treats it as impractical inside GUE and drops such packets. The source bundle contains duplicated commit identifiers and ambiguous version entries; branch-specific applicability should be confirmed against stable commits or vendor advisories.
Mitigation direction
Inventory Linux systems receiving GUE traffic and record their kernel builds.
Apply vendor kernel updates containing the appropriate stable fix for each maintained branch.
Consult Linux distribution or appliance-vendor guidance for confirmed fixed package versions.
Prioritize externally reachable GUE endpoints and systems where memory exhaustion would cause material disruption.
Validation and detection
Confirm each installed kernel includes the corresponding stable commit or an authenticated vendor backport.
Verify no affected kernel builds remain on systems that process untrusted GUE traffic.
Review network paths to determine whether untrusted GUE packets can reach potentially affected receivers.
Monitor relevant systems for abnormal kernel memory growth and packet-processing instability after remediation.
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-23095 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.