ipv6: addrconf: fix temp address generation after prefix deprecation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 76f793e3a47139d340185cbc1a314740c09b13d3 · < 4df5597c65446135362f72880995e8920f058fa0| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel can stop generating temporary IPv6 privacy addresses for a prefix after a router deprecates that prefix and later restores it. This can occur when a Router Advertisement sets the preferred lifetime to zero or the lifetime expires; the failure persists when the existing temporary address expires.
Engineers running Linux kernels that generate temporary IPv6 privacy addresses should check their systems; affected versions were not provided.