<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 13:44:00 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72429</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72429</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-72429</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1229 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1229</link>
      <description>certfr-2026-avi-1229</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1229</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72429</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72429</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: fix type confusion of dst_entry&lt;/p&gt;
&lt;p&gt;IOAM uses a dummy dst_entry(null_dst) to mark that the destination should
not be changed after the transformation. This dst is stored in the IOAM lwt
state and may be passed to dst_cache_set_ip6().&lt;/p&gt;
&lt;p&gt;However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which
treats the dst_entry as part of a struct rt6_info. Since the null_dst was
embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted
in an invalid cast and rt6_get_cookie() reading fields from the wrong
object.&lt;/p&gt;
&lt;p&gt;In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but
rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is
zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which
can become zero, making this a potential invalid pointer access.&lt;/p&gt;
&lt;p&gt;Fix this by embedding a full struct rt6_info for the dummy IPv6 route and
passing its dst member to the dst APIs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: fix type confusion of dst_entry&lt;/p&gt;
&lt;p&gt;IOAM uses a dummy dst_entry(null_dst) to mark that the destination should
not be changed after the transformation. This dst is stored in the IOAM lwt
state and may be passed to dst_cache_set_ip6().&lt;/p&gt;
&lt;p&gt;However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which
treats the dst_entry as part of a struct rt6_info. Since the null_dst was
embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted
in an invalid cast and rt6_get_cookie() reading fields from the wrong
object.&lt;/p&gt;
&lt;p&gt;In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but
rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is
zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which
can become zero, making this a potential invalid pointer access.&lt;/p&gt;
&lt;p&gt;Fix this by embedding a full struct rt6_info for the dummy IPv6 route and
passing its dst member to the dst APIs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72429</guid>
    </item>
    <item>
      <title>GHSA-34fv-pgg7-6wvm</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-34fv-pgg7-6wvm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: fix type confusion of dst_entry&lt;/p&gt;
&lt;p&gt;IOAM uses a dummy dst_entry(null_dst) to mark that the destination should
not be changed after the transformation. This dst is stored in the IOAM lwt
state and may be passed to dst_cache_set_ip6().&lt;/p&gt;
&lt;p&gt;However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which
treats the dst_entry as part of a struct rt6_info. Since the null_dst was
embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted
in an invalid cast and rt6_get_cookie() reading fields from the wrong
object.&lt;/p&gt;
&lt;p&gt;In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but
rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is
zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which
can become zero, making this a potential invalid pointer access.&lt;/p&gt;
&lt;p&gt;Fix this by embedding a full struct rt6_info for the dummy IPv6 route and
passing its dst member to the dst APIs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: ioam: fix type confusion of dst_entry&lt;/p&gt;
&lt;p&gt;IOAM uses a dummy dst_entry(null_dst) to mark that the destination should
not be changed after the transformation. This dst is stored in the IOAM lwt
state and may be passed to dst_cache_set_ip6().&lt;/p&gt;
&lt;p&gt;However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which
treats the dst_entry as part of a struct rt6_info. Since the null_dst was
embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted
in an invalid cast and rt6_get_cookie() reading fields from the wrong
object.&lt;/p&gt;
&lt;p&gt;In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but
rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is
zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which
can become zero, making this a potential invalid pointer access.&lt;/p&gt;
&lt;p&gt;Fix this by embedding a full struct rt6_info for the dummy IPv6 route and
passing its dst member to the dst APIs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-34fv-pgg7-6wvm</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72429</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72429</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix type confusion of dst_entry IOAM uses a dummy dst_entry(null_dst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to dst_cache_set_ip6(). However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which treats the dst_entry as part of a struct rt6_info. Since the null_dst was embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted in an invalid cast and rt6_get_cookie() reading fields from the wrong object. In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which can become zero, making this a potential invalid pointer access. Fix this by embedding a full struct rt6_info for the dummy IPv6 route and passing its dst member to the dst APIs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix type confusion of dst_entry IOAM uses a dummy dst_entry(null_dst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to dst_cache_set_ip6(). However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which treats the dst_entry as part of a struct rt6_info. Since the null_dst was embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted in an invalid cast and rt6_get_cookie() reading fields from the wrong object. In practice, the wrong cookie is not used while dst-&amp;gt;obsolete is zero, but rt6_get_cookie() may also access per-cpu value when rt-&amp;gt;sernum is zero. In this case, rt-&amp;gt;sernum aliases ioam6_lwt::cache::reset_ts, which can become zero, making this a potential invalid pointer access. Fix this by embedding a full struct rt6_info for the dummy IPv6 route and passing its dst member to the dst APIs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72429</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
