<?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 15:42:33 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98122</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98122</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del()&lt;/p&gt;
&lt;p&gt;vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every
MDBE_ATTR_SRC_LIST member, accepts the all-zeros address.&lt;/p&gt;
&lt;p&gt;A source list is only accepted on a (*, G) entry, whose source is the
all-zeros address, and for each member of the list an (S, G) entry is
derived from it by substituting the source. Entries are keyed by a plain
memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present
and holds the all-zeros address and the source list holds it as well, the
derived (S, G) key is byte-identical to the (*, G) key and resolves to the
same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is
then left with a zero address family.&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_del() removes the forwarding entry of a source before
freeing the source entry:&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr);
	vxlan_mdb_remote_src_entry_del(ent);&lt;/p&gt;
&lt;p&gt;With the keys aliased, the first call deletes the remote of the entry that
owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second
call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and
-&amp;gt;next out of it and writes through them.&lt;/p&gt;
&lt;p&gt;Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the
all-zeros source for deletion and reaches this from the sweep at the end
of vxlan_mdb_remote_srcs_replace().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&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;vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del()&lt;/p&gt;
&lt;p&gt;vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every
MDBE_ATTR_SRC_LIST member, accepts the all-zeros address.&lt;/p&gt;
&lt;p&gt;A source list is only accepted on a (*, G) entry, whose source is the
all-zeros address, and for each member of the list an (S, G) entry is
derived from it by substituting the source. Entries are keyed by a plain
memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present
and holds the all-zeros address and the source list holds it as well, the
derived (S, G) key is byte-identical to the (*, G) key and resolves to the
same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is
then left with a zero address family.&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_del() removes the forwarding entry of a source before
freeing the source entry:&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr);
	vxlan_mdb_remote_src_entry_del(ent);&lt;/p&gt;
&lt;p&gt;With the keys aliased, the first call deletes the remote of the entry that
owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second
call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and
-&amp;gt;next out of it and writes through them.&lt;/p&gt;
&lt;p&gt;Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the
all-zeros source for deletion and reaches this from the sweep at the end
of vxlan_mdb_remote_srcs_replace().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98122</guid>
    </item>
    <item>
      <title>GHSA-4jrj-q762-xjh5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-4jrj-q762-xjh5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del()&lt;/p&gt;
&lt;p&gt;vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every
MDBE_ATTR_SRC_LIST member, accepts the all-zeros address.&lt;/p&gt;
&lt;p&gt;A source list is only accepted on a (*, G) entry, whose source is the
all-zeros address, and for each member of the list an (S, G) entry is
derived from it by substituting the source. Entries are keyed by a plain
memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present
and holds the all-zeros address and the source list holds it as well, the
derived (S, G) key is byte-identical to the (*, G) key and resolves to the
same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is
then left with a zero address family.&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_del() removes the forwarding entry of a source before
freeing the source entry:&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr);
	vxlan_mdb_remote_src_entry_del(ent);&lt;/p&gt;
&lt;p&gt;With the keys aliased, the first call deletes the remote of the entry that
owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second
call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and
-&amp;gt;next out of it and writes through them.&lt;/p&gt;
&lt;p&gt;Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the
all-zeros source for deletion and reaches this from the sweep at the end
of vxlan_mdb_remote_srcs_replace().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&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;vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del()&lt;/p&gt;
&lt;p&gt;vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every
MDBE_ATTR_SRC_LIST member, accepts the all-zeros address.&lt;/p&gt;
&lt;p&gt;A source list is only accepted on a (*, G) entry, whose source is the
all-zeros address, and for each member of the list an (S, G) entry is
derived from it by substituting the source. Entries are keyed by a plain
memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present
and holds the all-zeros address and the source list holds it as well, the
derived (S, G) key is byte-identical to the (*, G) key and resolves to the
same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is
then left with a zero address family.&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_del() removes the forwarding entry of a source before
freeing the source entry:&lt;/p&gt;
&lt;p&gt;vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr);
	vxlan_mdb_remote_src_entry_del(ent);&lt;/p&gt;
&lt;p&gt;With the keys aliased, the first call deletes the remote of the entry that
owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second
call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and
-&amp;gt;next out of it and writes through them.&lt;/p&gt;
&lt;p&gt;Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the
all-zeros source for deletion and reaches this from the sweep at the end
of vxlan_mdb_remote_srcs_replace().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-4jrj-q762-xjh5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98122</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98122</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every MDBE_ATTR_SRC_LIST member, accepts the all-zeros address. A source list is only accepted on a (*, G) entry, whose source is the all-zeros address, and for each member of the list an (S, G) entry is derived from it by substituting the source. Entries are keyed by a plain memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present and holds the all-zeros address and the source list holds it as well, the derived (S, G) key is byte-identical to the (*, G) key and resolves to the same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is then left with a zero address family. vxlan_mdb_remote_src_del() removes the forwarding entry of a source before freeing the source entry: 	vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr); 	vxlan_mdb_remote_src_entry_del(ent); With the keys aliased, the first call deletes the remote of the entry that owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and -&amp;gt;next out of it and writes through them. Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the all-zeros source for deletion and reaches this from the sweep at the end of vxlan_mdb_remote_srcs_replace().   BUG: KASAN: slab-use-after-free in __vxlan_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() vxlan_mdb_is_valid_source(), which validates MDBE_ATTR_SOURCE and every MDBE_ATTR_SRC_LIST member, accepts the all-zeros address. A source list is only accepted on a (*, G) entry, whose source is the all-zeros address, and for each member of the list an (S, G) entry is derived from it by substituting the source. Entries are keyed by a plain memcmp() of struct vxlan_mdb_entry_key, so if MDBE_ATTR_SOURCE is present and holds the all-zeros address and the source list holds it as well, the derived (S, G) key is byte-identical to the (*, G) key and resolves to the same entry. Omitting MDBE_ATTR_SOURCE is not equivalent, as the key is then left with a zero address family. vxlan_mdb_remote_src_del() removes the forwarding entry of a source before freeing the source entry: 	vxlan_mdb_remote_src_fwd_del(vxlan, group, remote, &amp;amp;ent-&amp;gt;addr); 	vxlan_mdb_remote_src_entry_del(ent); With the keys aliased, the first call deletes the remote of the entry that owns &amp;#39;ent&amp;#39; instead of a separate (S, G) entry, and frees &amp;#39;ent&amp;#39;. The second call then runs on the freed entry, and its hlist_del() reads -&amp;gt;pprev and -&amp;gt;next out of it and writes through them. Adding the (*, G) entry with NLM_F_REPLACE and no source list marks the all-zeros source for deletion and reaches this from the sweep at the end of vxlan_mdb_remote_srcs_replace().   BUG: KASAN: slab-use-after-free in __vxlan_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98122</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
