ip6_gre: fix hardware header length for NBMA tunnels
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 832ba596494b2c9eac7760259eff2d8b7dcad0ee · < b8282668d8fa7c61b80e8e4890729031c291a16c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel incorrectly includes the lower device’s hardware header length in the hardware header length of NBMA ip6gre tunnels. The input does not describe what an attacker can do or specify access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with NBMA ip6gre tunnels should check their systems; affected versions are not specified.