Answer in brief
CVE-2026-64132 records a Unknown severity vulnerability in ipv6: ioam: refresh hdr pointer before ioam6_event(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <769723124b7c3b2bfea4cf68ad292698b87c8d01 || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <24de676da63c1122d2c13b0d546238b66d1b4e62 || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <5af905aa8e91ff8d94572a1e089558f21dcf24ed || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <e46e6bc97fb1f339730ff1ba74267fbf48e7a422 | 769723124b7c3b2bfea4cf68ad292698b87c8d01, 24de676da63c1122d2c13b0d546238b66d1b4e62, 5af905aa8e91ff8d94572a1e089558f21dcf24ed, e46e6bc97fb1f339730ff1ba74267fbf48e7a422 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64132 records a Unknown severity vulnerability in ipv6: ioam: refresh hdr pointer before ioam6_event(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <769723124b7c3b2bfea4cf68ad292698b87c8d01 || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <24de676da63c1122d2c13b0d546238b66d1b4e62 || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <5af905aa8e91ff8d94572a1e089558f21dcf24ed || >=f655c78d6225f585ef60a9d93ffb79d507ff3ad3 <e46e6bc97fb1f339730ff1ba74267fbf48e7a422 | 769723124b7c3b2bfea4cf68ad292698b87c8d01, 24de676da63c1122d2c13b0d546238b66d1b4e62, 5af905aa8e91ff8d94572a1e089558f21dcf24ed, e46e6bc97fb1f339730ff1ba74267fbf48e7a422 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.