CVE-2026-97472ipv6: addrconf: fix temp address generation after prefix deprecation
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 9 days later
· 9 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < b00f7c1da82a809156f785ed37536c2d2584927d
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < 6da8ba900b85e6478e211427630c67595fb707a4
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < 4f7d2a8dc364c4e55d0a1533451339008512933f
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < f601ec5c92b3260c742f27a5d2fd289e30ae798f
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < bff7b87dfa28a1502c18d0c6f1fadda5162fa854
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < 4df5597c65446135362f72880995e8920f058fa0
- affected 76f793e3a47139d340185cbc1a314740c09b13d3 – < e20d8922aa8fe441d291364c96c2179a005b79ea
- affected 3.2
- unaffected < 3.2
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/b00f7c1da82a809156f785ed37536c2d2584927d (opens in a new tab)
- https://git.kernel.org/stable/c/6da8ba900b85e6478e211427630c67595fb707a4 (opens in a new tab)
- https://git.kernel.org/stable/c/4f7d2a8dc364c4e55d0a1533451339008512933f (opens in a new tab)
- https://git.kernel.org/stable/c/f601ec5c92b3260c742f27a5d2fd289e30ae798f (opens in a new tab)
- https://git.kernel.org/stable/c/bff7b87dfa28a1502c18d0c6f1fadda5162fa854 (opens in a new tab)
- https://git.kernel.org/stable/c/4df5597c65446135362f72880995e8920f058fa0 (opens in a new tab)
- https://git.kernel.org/stable/c/e20d8922aa8fe441d291364c96c2179a005b79ea (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86070 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97472)Record last updated .