Skip to content
VulniPulse
Advisory severityHigh7.0Red Hat Linux

High [CVE-2026-64132] refresh hdr pointer before ioam6_event

This high-severity Red Hat Linux advisory covers CVE-2026-64132 affecting Red Hat Enterprise Linux 10, Shadow Migration Toolkit for Virtualization for RHEL 10, Red Hat package: kernel.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-64132 Source published Source updated

VulniPulse record published Record updated

CVE-2026-64132
Affected products & platforms
Red Hat LinuxLinux Kernel
Open source advisory

Get an email when Red Hat Linux Linux Kernel publishes the next one.

See Red Hat Linux Linux Kernel's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux Linux Kernel

Summary

In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: refresh hdr pointer before ioam6_event() Reported by Sashiko: In ipv6_hop_ioam(), the hdr pointer is initialized to point into the skb's linear data buffer.

Later, the code calls skb_ensure_writable(), which might reallocate the buffer: if (skb_ensure_writable(skb, optoff + 2 + hdr->opt_len)) goto drop; /* Trace pointer may have changed */ trace = (struct ioam6_trace_hdr *)(skb_network_header(skb) + optoff + sizeof(*hdr)); ioam6_fill_trace_data(skb, ns, trace, true); ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb->dev), GFP_ATOMIC, (void *)trace, hdr->opt_len - 2); If the skb is cloned or lacks sufficient linear headroom, skb_ensure_writable() will invoke pskb_expand_head(), which reallocates the skb's data buffer and frees the old one, invalidating pointers to it.

While the code recalculates the trace pointer immediately after the call to skb_ensure_writable(), it fails to recalculate the hdr pointer. This patch fixes the above by recalculating the hdr pointer before passing hdr->opt_len to ioam6_event(), so that we avoid any UaF.

A flaw was found in the Linux kernel's IPv6 In-situ Operations, Administration, and Maintenance (IOAM) component. This vulnerability, a use-after-free, occurs when the kernel fails to correctly update a pointer after reallocating a network packet's buffer.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Fixed versions
  • kernel-0:6.12.0-211.63.1.el10_2
  • RHSA-2026:76738

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Ensure IPv6 In-situ Operations, Administration, and Maintenance (IOAM) processing is disabled across all network interfaces. By default, IOAM processing is disabled (value set to 0). If it has been enabled, disable it dynamically using sysctl: # sysctl -w net.ipv6.conf.all.ioam6_enabled=0 # sysctl -w net.ipv6.conf.default.ioam6_enabled=0 To persist these settings across system reboots, create a file in /etc/sysctl.d/: # cat << 'EOF' > /etc/sysctl.d/99-disable-ioam.conf net.ipv6.conf.all.ioam6_enabled = 0 net.ipv6.conf.default.ioam6_enabled = 0 EOF # sysctl --system Caveats: Disabling IOAM prevents the kernel from processing IPv6 IOAM trace options, which will impact network telemetry or diagnostic utilities relying on in-situ telemetry data. Warning: Runtime sysctl modifications take effect immediately without requiring a system restart; however, verify that interface-specific sysctl entries (net.ipv6.conf.<interface>.ioam6_enabled) are also set to 0 if previously configured.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.