CVE-2026-74747: ipvs: revalidate ihl to prevent out-of-bounds access

Published Aug 26, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ipvs: revalidate ihl to prevent out-of-bounds access

While the outer IP header is already pulled into the skb head, we must be careful and revalidate the embedded headers after reading them from the skb frags to prevent out-of-bounds access.

One such place reported by Sashiko is ipvsnaticmp() where local process can change the ihl field and after skbensurewritable() we can see larger value which is a problem for the ipsendcheck(cih) calls.

Add check to drop the packet if the ihl field is changed.

Affected Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel (ipvs) to a version that resolves this vulnerability.

    Patch ipvs: revalidate ihl to prevent out-of-bounds access
  2. Configuration

    Update the IPVS NAT ICMP path (ip_vs_nat_icmp()) to revalidate the outer/embedded IP header IHL after potential changes by the local process, preventing out-of-bounds access when computing/using values for ip_send_check(cih) and reading from skb frags.

    ip_vs_nat_icmp() (IPVS in Linux kernel) IHL revalidation behavior = Revalidate the ihl field (and embedded headers) before using it to access skb frags / embedded headers to prevent out-of-bounds access

Event History

Aug 26, 2026
CVE Published
via MITRE·02:36 PM
Data Sourced
via MITRE·02:36 PM
Description
Data Sourced
via NVD·03:16 PM
Description

Frequently Asked Questions

1

What conditions are needed to trigger the issue?

The affected path is ip_vs_nat_icmp() in Linux IPVS processing. The issue occurs when a local process can modify an embedded IP header's IHL field after the header has been read from skb fragments and skb_ensure_writable() is called.

2

What is the impact of a successful trigger?

A changed IHL value can cause subsequent processing, including ip_send_check(cih), to access data out of bounds. The fix drops packets when the IHL field changes during this processing.

3

What mitigation is available if the fix cannot be deployed immediately?

The provided information identifies the problematic condition as local modification of the packet's embedded IHL field during IPVS ICMP NAT handling. No configuration workaround or temporary mitigation is specified.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203