ipvs: clear IPv4 options after rebasing tunnel ICMP errors
- 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 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, and 2 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
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ipvs: clear IPv4 options after rebasing tunnel ICMP errors ip_vs_in_icmp() rebases an skb from the outer ICMP packet to the quoted original request before passing it to icmp_send(). However, IPCB(skb)->opt still describes the outer IPv4 header. A timestamp option in the outer header can therefore leave an offset that points into the quoted transport header after the rebase. __ip_options_echo() treats a byte at that stale location as the option length and copies it into the fixed-size option storage on the __icmp_send() stack, causing a stack out-of-bounds write. Clear the stale option metadata after resetting the network header. Keep the remaining control block fields, including the ingress interface used by the ICMP response path.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in 79ffa99202c944467e28b13b513bf2998732edff; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in c9413b50204738fbc429bb86bf01353c393a6c28; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in 37c61b3745129cbd682c557b51345828120972e5; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in ed246dd85ebf27c1f6b7897834d40786c0ca3006; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in 6f46fc460e9316062bdcdf89199eb5d7a33da33b; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in 75eec935444db4af2123e0491936f6e273d7ea00; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in 384b4dae14277d369221d187e9b3af56c79d2e50; From f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e · fixed in e0ba936287dfe9783426aac27e5fd76fe35b38c9
- Linux Linux
3.7
- KernelLinux
From 3.7.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.152; From 6.7.0 · fixed in 6.12.104; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9
References 8
git.kernel.org
- stable/c/79ffa99202c944467e28b13b513bf2998732edff
- stable/c/c9413b50204738fbc429bb86bf01353c393a6c28
- stable/c/37c61b3745129cbd682c557b51345828120972e5
- stable/c/ed246dd85ebf27c1f6b7897834d40786c0ca3006
- stable/c/6f46fc460e9316062bdcdf89199eb5d7a33da33b
- stable/c/75eec935444db4af2123e0491936f6e273d7ea00
- stable/c/384b4dae14277d369221d187e9b3af56c79d2e50
- stable/c/e0ba936287dfe9783426aac27e5fd76fe35b38c9