ip6_gre: fix hardware header length for NBMA tunnels
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.20, 5.5, 5.10, 5.10.270, 5.15.221, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in cb1afd087aedc90e5274537e4fb9bf3f98e5afdb; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in 7719f6e7ed2ffddc2c3bb61f4467b76d49e0af6a; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in b1e95e3602d8e112458627f14c6c31c21f2188cb; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in c3457a5aae5fb43f7023d3f3dc472c2afa22acf0; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in 8bfe746afee38dd6e4348ddcd22d554789dbb9ff; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in b8282668d8fa7c61b80e8e4890729031c291a16c; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in 565038b0092f65afe384961c0f548d605bf438b9; From 832ba596494b2c9eac7760259eff2d8b7dcad0ee · fixed in 505b6d296c486ef7d1274f279d4c43a172f63224; From 4.19.162 · fixed in 4.20; From 5.4.82 · fixed in 5.5; From 5.9.13 · fixed in 5.10
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/cb1afd087aedc90e5274537e4fb9bf3f98e5afdb
- stable/c/7719f6e7ed2ffddc2c3bb61f4467b76d49e0af6a
- stable/c/b1e95e3602d8e112458627f14c6c31c21f2188cb
- stable/c/c3457a5aae5fb43f7023d3f3dc472c2afa22acf0
- stable/c/8bfe746afee38dd6e4348ddcd22d554789dbb9ff
- stable/c/b8282668d8fa7c61b80e8e4890729031c291a16c
- stable/c/565038b0092f65afe384961c0f548d605bf438b9
- stable/c/505b6d296c486ef7d1274f279d4c43a172f63224