In the Linux kernel, the following vulnerability has been resolved: ipvs: clear IPv4 options after rebasing tunnel ICMP errors ip_vs_in…
CVE-2026-74669 · published 22 Aug 2026
How serious is it
- Severity: critical, CVSS score 9.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74669?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 3.7
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/37c61b3745129cbd682c557b51345828120972e5
- git.kernel.org/stable/c/384b4dae14277d369221d187e9b3af56c79d2e50
- git.kernel.org/stable/c/6f46fc460e9316062bdcdf89199eb5d7a33da33b
- git.kernel.org/stable/c/75eec935444db4af2123e0491936f6e273d7ea00
- git.kernel.org/stable/c/79ffa99202c944467e28b13b513bf2998732edff
- git.kernel.org/stable/c/c9413b50204738fbc429bb86bf01353c393a6c28
- git.kernel.org/stable/c/e0ba936287dfe9783426aac27e5fd76fe35b38c9
- git.kernel.org/stable/c/ed246dd85ebf27c1f6b7897834d40786c0ca3006
Merged from NVD. Last updated 24 Oct 2026. All vulnerabilities · RSS · JSON