{"id":"CVE-2026-97472","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: addrconf: fix temp address generation after prefix deprecation\n\nWhen a router temporarily deprecates an IPv6 prefix (either by sending a\nRouter Advertisement with…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: addrconf: fix temp address generation after prefix deprecation\n\nWhen a router temporarily deprecates an IPv6 prefix (either by sending a\nRouter Advertisement with…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bff7b87dfa28a1502c18d0c6f1fadda5162fa854","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4df5597c65446135362f72880995e8920f058fa0","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e20d8922aa8fe441d291364c96c2179a005b79ea","Linux < 6.12.111","Linux < 6.18.53","Linux (all versions)"],"published":"2026-09-24","updated":"2026-09-24","sourceUpdated":"2026-09-24T17:17:24.273","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97472","references":[{"url":"https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-24T16:47:15.873Z","slug":"CVE-2026-97472","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: addrconf: fix temp address generation after prefix deprecation\n\nWhen a router temporarily deprecates an IPv6 prefix (either by sending a\nRouter Advertisement with Preferred Lifetime = 0 or by letting the\nlifetime expire) and later restores it, the kernel permanently loses its\nability to generate temporary privacy addresses (RFC 8981) for that\nprefix.\n\nThis happens because the address worker attempts to generate a\nreplacement temporary address when the current one nears expiration. As\nthe base prefix is deprecated already, the generation fails after\nmarking the temporary address as already having spawned a replacement\n(ifp->regen_count++).\n\nWhen the router eventually restores the prefix, the temporary address\nbecomes active again. However, once it naturally expires, the address\nworker sees this temporary address already tried to generate one and\nskips the regeneration.\n\nFix the issue by resetting the regen_count check of the latest temp\naddress generated for the prefix updated by the incoming RA.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}