CVE-2026-80844

xfrm: ah6: validate routing header segments_left

N/A
Published: September 4, 2026 at 03:54 PM UTC
Updated: October 19, 2026 at 09:17 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.4%

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: ah6: validate routing header segments_left AH6 rearranges routing-header addresses before computing or verifying the ICV. ipv6_rearrange_rthdr() assumes that segments_left is not larger than the number of addresses described by the routing header's hdrlen field. That assumption does not hold for raw IPv6 HDRINCL packets. A packet with hdrlen equal to 2 describes one address, but can carry an arbitrary segments_left value. With segments_left equal to 255, the function moves its address pointer 4,064 bytes backwards and passes a 4,064-byte length to memmove(), resulting in an out-of-bounds access. Validate the invariant locally before modifying the routing header or performing any address-pointer arithmetic, and propagate malformed-header errors to the existing AH6 input and output error paths.

Affected

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

Vendor states this is fixed in 0bf11081ad3753938a2b48723ce6298dbac743a1 (fixed)
Vendor states this is fixed in 1516e31ac458a738be485620579d8f7fb2700fcb (fixed)
Vendor states this is fixed in 1b7e066eabcc7d6d8f476c34739b45932f2f4c31 (fixed)
Vendor states this is fixed in 2dc650956e4e163b879b3fb1027f9557abc5c985 (fixed)
Vendor states this is fixed in 46640c814f25f096b0b0045ca50e1b7030cd8a30 (fixed)
Vendor states this is fixed in 48b0e36cf54358276ee7aa897034c973097d2bc9 (fixed)
Vendor states this is fixed in 6733ae71268a27d598cfb3f3339a3c950b9b656d (fixed)
Vendor states this is fixed in 7bad4bda74dc4713f398d3b7624ff05478e3a568 (fixed)
Vendor states this is fixed in f00df8500e5a36ba70d336fd34bd2152ea074e5f (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.269 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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