Bug 2521375 (CVE-2026-74669) - CVE-2026-74669 kernel: ipvs: clear IPv4 options after rebasing tunnel ICMP errors
Summary: CVE-2026-74669 kernel: ipvs: clear IPv4 options after rebasing tunnel ICMP er...
Keywords:
Status: NEW
Alias: CVE-2026-74669
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-22 15:42 UTC by OSIDB Bzimport
Modified: 2026-10-08 09:50 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:75746 0 None None None 2026-10-05 10:48:53 UTC
Red Hat Product Errata RHSA-2026:75747 0 None None None 2026-10-05 11:24:00 UTC
Red Hat Product Errata RHSA-2026:76738 0 None None None 2026-10-07 20:28:58 UTC
Red Hat Product Errata RHSA-2026:76739 0 None None None 2026-10-08 09:50:25 UTC

Description OSIDB Bzimport 2026-08-22 15:42:26 UTC
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.

Comment 3 Jon Orris 2026-10-05 10:48:52 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75746 https://access.redhat.com/errata/RHSA-2026:75746

Comment 4 Jon Orris 2026-10-05 11:23:58 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75747 https://access.redhat.com/errata/RHSA-2026:75747

Comment 5 Jon Orris 2026-10-07 20:28:56 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:76738 https://access.redhat.com/errata/RHSA-2026:76738

Comment 6 Jon Orris 2026-10-08 09:50:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:76739 https://access.redhat.com/errata/RHSA-2026:76739


Note You need to log in before you can comment on or make changes to this bug.