Strix
74.8K

CVE-2026-97472

UnknownEPSS 0.17%

Last modified

CVE-2026-97472 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

5.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 76f793e3a47139d340185cbc1a314740c09b13d3, < b00f7c1da82a809156f785ed37536c2d2584927d; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < 6da8ba900b85e6478e211427630c67595fb707a4; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < 4f7d2a8dc364c4e55d0a1533451339008512933f; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < f601ec5c92b3260c742f27a5d2fd289e30ae798f; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < bff7b87dfa28a1502c18d0c6f1fadda5162fa854; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < 4df5597c65446135362f72880995e8920f058fa0; >= 76f793e3a47139d340185cbc1a314740c09b13d3, < e20d8922aa8fe441d291364c96c2179a005b79ea
LinuxLinux3.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97472?
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.
How severe is CVE-2026-97472?
Severity scoring for CVE-2026-97472 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-97472?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-97472?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST