Skip to main content
VulnerabilityPublished

CVE-2026-99708: Linux kernel · ipv6: reject wrapped temporary address preferred lifetimes

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99708· Medium

Not known to be exploited · fixed in c3e67bd82b9b9b1a5118f09a429ccefe2aab0741 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in c3e67bd82b9b9b1a5118f09a429ccefe2aab0741, 56758052466e6617fa4ac8e68d3c109cca56efb3, 11c7029932fb578b12b379a5559702b0cec8feda +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to c3e67bd82b9b9b1a5118f09a429ccefe2aab0741, 56758052466e6617fa4ac8e68d3c109cca56efb3, 11c7029932fb578b12b379a5559702b0cec8feda or 6bbce146f893ab8b335e9eb82f4293bc94f3a4bf.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9, < c3e67bd82b9b9b1a5118f09a429ccefe2aab0741
Fixed in
  • c3e67bd82b9b9b1a5118f09a429ccefe2aab0741
LinuxLinuxAffected
  • ≥ f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9, < 56758052466e6617fa4ac8e68d3c109cca56efb3
Fixed in
  • 56758052466e6617fa4ac8e68d3c109cca56efb3
LinuxLinuxAffected
  • ≥ f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9, < 11c7029932fb578b12b379a5559702b0cec8feda
Fixed in
  • 11c7029932fb578b12b379a5559702b0cec8feda
LinuxLinuxAffected
  • ≥ f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9, < 6bbce146f893ab8b335e9eb82f4293bc94f3a4bf
Fixed in
  • 6bbce146f893ab8b335e9eb82f4293bc94f3a4bf
LinuxLinuxAffected
  • =6.9
Fixed in–

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.

References

Community reviews

Loading reviews…