CVE-2026-89562High· 7.8▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: ip6_gre: fix hardware header length for NBMA tunnels ip6gre_tnl_link_config_route() accumulates the lower device's hardware header length into dev->hard_header_len whe…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
— → 7.8
none → high
0.2% → 0.2%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
ip6_gre: fix hardware header length for NBMA tunnels
ip6gre_tnl_link_config_route() accumulates the lower device's hardware header length into dev->hard_header_len whenever header_ops is set. This is incorrect for both users of header_ops.
ip6gretap and ip6erspan have a fixed Ethernet hardware header length. For an NBMA ip6gre tunnel, ip6gre_header() creates only the GRE header, the optional FOU or GUE header, and the outer IPv6 header. The lower device header is headroom needed later, not part of the tunnel device's hardware header.
Keep the lower device header in needed_headroom. Set hard_header_len to the tunnel header length only for ARPHRD_IP6GRE devices with header_ops, and leave the fixed Ethernet header length unchanged for tap and erspan devices.
Linux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < cb1afd087aedc90e5274537e4fb9bf3f98e5afdbLinux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < 7719f6e7ed2ffddc2c3bb61f4467b76d49e0af6aLinux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < b1e95e3602d8e112458627f14c6c31c21f2188cbLinux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < c3457a5aae5fb43f7023d3f3dc472c2afa22acf0Linux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < 8bfe746afee38dd6e4348ddcd22d554789dbb9ffLinux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < b8282668d8fa7c61b80e8e4890729031c291a16cLinux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < 565038b0092f65afe384961c0f548d605bf438b9Linux >= 832ba596494b2c9eac7760259eff2d8b7dcad0ee < 505b6d296c486ef7d1274f279d4c43a172f63224Linux cf3d9717a5271573fa193c4dfa0df856295d5b15Linux 187a6daf5db45adc807c85bbe285319107bed198Linux d9897bb66ce989325b4bf4cdbb6a799e4ac878b6Linux >= 4.19.162 < 4.20Linux >= 5.4.82 < 5.5Linux >= 5.9.13 < 5.10Linux 5.10Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets