{"api_version":"1","generated_at":"2026-10-01T16:18:26+00:00","cve":"CVE-2026-97472","urls":{"html":"https://cve.report/CVE-2026-97472","api":"https://cve.report/api/cve/CVE-2026-97472.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97472","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97472"},"summary":{"title":"ipv6: addrconf: fix temp address generation after prefix deprecation","description":"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 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 17:17:24","updated_at":"2026-09-28 06:16:33"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0","name":"https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea","name":"https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854","name":"https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97472","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97472","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 76f793e3a47139d340185cbc1a314740c09b13d3 bff7b87dfa28a1502c18d0c6f1fadda5162fa854 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 76f793e3a47139d340185cbc1a314740c09b13d3 4df5597c65446135362f72880995e8920f058fa0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 76f793e3a47139d340185cbc1a314740c09b13d3 e20d8922aa8fe441d291364c96c2179a005b79ea git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97472","cve":"CVE-2026-97472","epss":"0.001660000","percentile":"0.052060000","score_date":"2026-09-29","updated_at":"2026-09-30 00:11:23"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/ipv6/addrconf.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bff7b87dfa28a1502c18d0c6f1fadda5162fa854","status":"affected","version":"76f793e3a47139d340185cbc1a314740c09b13d3","versionType":"git"},{"lessThan":"4df5597c65446135362f72880995e8920f058fa0","status":"affected","version":"76f793e3a47139d340185cbc1a314740c09b13d3","versionType":"git"},{"lessThan":"e20d8922aa8fe441d291364c96c2179a005b79ea","status":"affected","version":"76f793e3a47139d340185cbc1a314740c09b13d3","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/ipv6/addrconf.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.2"},{"lessThan":"3.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"3.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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 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."}],"providerMetadata":{"dateUpdated":"2026-09-28T05:30:00.197Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854"},{"url":"https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0"},{"url":"https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea"}],"title":"ipv6: addrconf: fix temp address generation after prefix deprecation","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97472","datePublished":"2026-09-24T16:04:14.951Z","dateReserved":"2026-09-24T16:01:01.148Z","dateUpdated":"2026-09-28T05:30:00.197Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 17:17:24","lastModifiedDate":"2026-09-28 06:16:33","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97472","Ordinal":"1","Title":"ipv6: addrconf: fix temp address generation after prefix depreca","CVE":"CVE-2026-97472","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97472","Ordinal":"1","NoteData":"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 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.","Type":"Description","Title":"ipv6: addrconf: fix temp address generation after prefix depreca"}]}}}