From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99708: ipv6: reject wrapped temporary address preferred lifetimes
Date: Fri, 20 Nov 2026 06:51:34 +0100 [thread overview]
Message-ID: <2026112005-CVE-2026-99708-47e2@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-99708 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 and fixed in 6.12.118 with commit 56758052466e6617fa4ac8e68d3c109cca56efb3
Issue introduced in 6.9 with commit f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 and fixed in 6.18.64 with commit 11c7029932fb578b12b379a5559702b0cec8feda
Issue introduced in 6.9 with commit f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 and fixed in 7.3.5 with commit 6bbce146f893ab8b335e9eb82f4293bc94f3a4bf
Issue introduced in 6.9 with commit f4bcbf360ac8dc424dc4d2b384b528e69b6f34d9 and fixed in 7.4-rc2 with commit c3e67bd82b9b9b1a5118f09a429ccefe2aab0741
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99708
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/ipv6/addrconf.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/56758052466e6617fa4ac8e68d3c109cca56efb3
https://git.kernel.org/stable/c/11c7029932fb578b12b379a5559702b0cec8feda
https://git.kernel.org/stable/c/6bbce146f893ab8b335e9eb82f4293bc94f3a4bf
https://git.kernel.org/stable/c/c3e67bd82b9b9b1a5118f09a429ccefe2aab0741
reply other threads:[~2026-11-20 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112005-CVE-2026-99708-47e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.