Skip to content
Threat Brief

← All advisories

CVE-2026-99708

Severity unknownNo known exploitationFix available

ipv6: reject wrapped temporary address preferred lifetimes

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: reject wrapped temporary address preferred lifetimes ipv6_create_tempaddr() raises a temporary address's preferred lifetime to regen_advance + age + 1 when the configured lifetime is too short. The result is stored in a u32, while regen_advance and age are unsigned long. If the sum wraps or is truncated, the stored lifetime can still be less than or equal to regen_advance + age. addrconf_verify_rtnl() then sees the new address as due for regeneration and creates another one. Temporary addresses are not limited by max_addresses since commit 4b08a8f1bd8c ("ipv6: remove max_addresses check from ipv6_create_tempaddr"), so this can cause unbounded address growth. With dad_transmits set to -1, a baseline kernel reached 2859 loopback addresses in two seconds. After storing the adjusted lifetime, verify that it is still greater than regen_advance + age. Reject the new address if the check fails. On an x86-64 KASAN kernel, the normal configuration created three IPv6 addresses. The negative dad_transmits, positive multiplication overflow, and large retransmission-time cases each left only the loopback and public addresses. An i386 defconfig and an x86-64 allmodconfig both built addrconf.o with W=1.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 before 11c7029932fb578b12b379a5559702b0cec8feda11c7029932fb578b12b379a5559702b0cec8fedaCVE Program
LinuxLinuxfrom f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 before 6bbce146f893ab8b335e9eb82f4293bc94f3a4bf6bbce146f893ab8b335e9eb82f4293bc94f3a4bfCVE Program
LinuxLinuxfrom f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 before c3e67bd82b9b9b1a5118f09a429ccefe2aab0741c3e67bd82b9b9b1a5118f09a429ccefe2aab0741CVE Program
LinuxLinuxfrom f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 before 56758052466e6617fa4ac8e68d3c109cca56efb356758052466e6617fa4ac8e68d3c109cca56efb3CVE Program
LinuxLinux6.9Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.9Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references