All vulnerabilities
CVE-2026-97472

Linux: ipv6: addrconf: fix temp address generation after prefix deprecation

Linux LinuxOperating systems
Open in ThreatlineRecord JSON
CVSS
NoneNot scored
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.17%Chance of exploitation activity in the next 30 days, higher than 6% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in6da8ba900b85e6478e211427630c67595fb707a4Also 4f7d2a8dc364c4e55d0a1533451339008512933f, 4df5597c65446135362f72880995e8920f058fa0CVE List
Published24 Sep 2026Updated 3 Oct 2026CVE List

What fixes it

  • 6da8ba900b85e6478e211427630c67595fb707a4LinuxCVE List
  • 4f7d2a8dc364c4e55d0a1533451339008512933fLinuxCVE List
  • 4df5597c65446135362f72880995e8920f058fa0LinuxCVE List

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 16

  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before b00f7c1da82a809156f785ed37536c2d2584927dCVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before 6da8ba900b85e6478e211427630c67595fb707a4CVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before 4f7d2a8dc364c4e55d0a1533451339008512933fCVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before f601ec5c92b3260c742f27a5d2fd289e30ae798fCVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before bff7b87dfa28a1502c18d0c6f1fadda5162fa854CVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before 4df5597c65446135362f72880995e8920f058fa0CVE List
  • Linuxaffected: 76f793e3a47139d340185cbc1a314740c09b13d3 before e20d8922aa8fe441d291364c96c2179a005b79eaCVE List
  • Linuxaffected: 3.2CVE List
  • Linuxunaffected: all versions before 3.2CVE List
  • Linuxunaffected: 5.10.271 through 5.10.*CVE List
  • Linuxunaffected: 5.15.222 through 5.15.*CVE List
  • Linuxunaffected: 6.1.189 through 6.1.*CVE List
  • Linuxunaffected: 6.6.158 through 6.6.*CVE List
  • Linuxunaffected: 6.12.111 through 6.12.*CVE List
  • Linuxunaffected: 6.18.53 through 6.18.*CVE List
  • Linuxunaffected: 7.2CVE List

References 7