<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:20:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99708 — ipv6: reject wrapped temporary address preferred lifetimes</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99708</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: reject wrapped temporary address preferred lifetimes&lt;/p&gt;
&lt;p&gt;ipv6_create_tempaddr() raises a temporary address&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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 (&amp;#34;ipv6: remove max_addresses
check from ipv6_create_tempaddr&amp;#34;), so this can cause unbounded address
growth. With dad_transmits set to -1, a baseline kernel reached 2859
loopback addresses in two seconds.&lt;/p&gt;
&lt;p&gt;After storing the adjusted lifetime, verify that it is still greater than
regen_advance + age. Reject the new address if the check fails.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: reject wrapped temporary address preferred lifetimes&lt;/p&gt;
&lt;p&gt;ipv6_create_tempaddr() raises a temporary address&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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 (&amp;#34;ipv6: remove max_addresses
check from ipv6_create_tempaddr&amp;#34;), so this can cause unbounded address
growth. With dad_transmits set to -1, a baseline kernel reached 2859
loopback addresses in two seconds.&lt;/p&gt;
&lt;p&gt;After storing the adjusted lifetime, verify that it is still greater than
regen_advance + age. Reject the new address if the check fails.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99708</guid>
    </item>
  </channel>
</rss>
