CVE-2026-98570

net: ipv6: keep room for the mac header in dst_dev_overhead()

N/A
Published: October 18, 2026 at 03:18 PM UTC
Updated: October 19, 2026 at 10:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: ipv6: keep room for the mac header in dst_dev_overhead() The seg6, ioam6 and rpl lwtunnels size their skb_cow_head() request as the length they are about to push plus dst_dev_overhead(), then push the new headers and rebuild the mac header below them with skb_mac_header_rebuild(). That rebuild needs skb->mac_len of headroom, but dst_dev_overhead() leaves LL_RESERVED_SPACE() of the egress device, 16 bytes for plain Ethernet. Where the mac header is longer than that, as it is on ingress through a VLAN device with reorder_hdr off, the rebuild runs out of room: skb_set_mac_header(skb, -skb->mac_len) computes a negative offset, stores it unchecked in the u16 skb->mac_header, and the memmove that follows writes skb->mac_len bytes about 64 KB past skb->head. Forwarding plain ping6 traffic through such a device reproduces it on all five seg6 encapsulation modes and on the rpl and ioam6 inline paths; skb->mac_header comes back as 65534 on a 704-byte head. Return the larger of the two. The helper already returns skb->mac_len when it has no dst, so this only makes the other branch agree, and it covers every caller rather than each call site in turn.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

25d8e065c7972dc98fd7a4cac322d5367eaede882fcc9f3798ef82399564d247458e69abd10e683b371d8dc298b4f59e99b4564ac5d906fce0932c694a855c5aec41bf84922224ab7a74e088776e3ac44c12c3c8abd8b888945d31e7bdbb0d8b73032fc55.10.2355.15.1796.1.1306.12.166.13.46.146.6.81634710a372ba65bee667c2f6e58a97658c639eab8471e228448a818e4c27cab4b681b2e758e46cf5a9f0407414e16176fdbbbd298c9e18d6dfdf96bcab9de9c48316d2622d3bf353916b99971570e2c9b26f015dfb07b6be12d005a0ed0c5c43b7bedbf3c0b11dc50590e10590b39dcda79835cd32f49d00c432cd18a07b623651ed15ea167bd303467004ccc447c5a9c47bb4858ab12bf90879fe595d2b7f46dce525185bc92864e5a318040285ee070563fe34
Vendor states this is fixed in 7.2.9 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card