CVE-2026-97472

ipv6: addrconf: fix temp address generation after prefix deprecation

N/A
Published: September 24, 2026 at 04:04 PM UTC
Updated: October 3, 2026 at 11: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.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: addrconf: fix temp address generation after prefix deprecation When a router temporarily deprecates an IPv6 prefix (either by sending a Router Advertisement with Preferred Lifetime = 0 or by letting the lifetime expire) and later restores it, the kernel permanently loses its ability to generate temporary privacy addresses (RFC 8981) for that prefix. This happens because the address worker attempts to generate a replacement temporary address when the current one nears expiration. As the base prefix is deprecated already, the generation fails after marking the temporary address as already having spawned a replacement (ifp->regen_count++). When the router eventually restores the prefix, the temporary address becomes active again. However, once it naturally expires, the address worker sees this temporary address already tried to generate one and skips the regeneration. Fix the issue by resetting the regen_count check of the latest temp address generated for the prefix updated by the incoming RA.

Affected

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

3.2 ≤ v < 5.10.2713.2 ≤ v < 5.15.2223.2 ≤ v < 6.1.1893.2 ≤ v < 6.12.1113.2 ≤ v < 6.18.533.2 ≤ v < 6.6.1583.2 ≤ v < 7.23.276f793e3a47139d340185cbc1a314740c09b13d3
Vendor states this is fixed in 4df5597c65446135362f72880995e8920f058fa0 (fixed)
Vendor states this is fixed in 4f7d2a8dc364c4e55d0a1533451339008512933f (fixed)
Vendor states this is fixed in 6da8ba900b85e6478e211427630c67595fb707a4 (fixed)
Vendor states this is fixed in b00f7c1da82a809156f785ed37536c2d2584927d (fixed)
Vendor states this is fixed in bff7b87dfa28a1502c18d0c6f1fadda5162fa854 (fixed)
Vendor states this is fixed in e20d8922aa8fe441d291364c96c2179a005b79ea (fixed)
Vendor states this is fixed in f601ec5c92b3260c742f27a5d2fd289e30ae798f (fixed)
Vendor states this is fixed in 3.2 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (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