<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T16:55:18.613689+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98103</id>
    <title>fkie_cve-2026-98103</title>
    <updated>2026-09-28T16:55:18.634686+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>igmp: convert struct ip_sf_list to RCU</p>
<p>Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu")
added spin_lock_bh(&amp;im-&gt;lock) to ip_check_mc_rcu() to prevent a
use-after-free while iterating im-&gt;sources during concurrent deletions.</p>
<p>However, ip_check_mc_rcu() is called from RCU read-side critical
sections in packet receive and route lookup fast paths (e.g.
__mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()).</p>
<p>When igmpv3_send_cr() or igmpv3_send_report() holds &amp;pmc-&gt;lock and
calls add_grec() -&gt; igmpv3_newpack() -&gt; ip_route_output_ports(),
an XFRM policy matching a multicast destination triggers
xfrm_tmpl_resolve_one() -&gt; xfrm4_get_saddr() -&gt; __mkroute_output() -&gt;
ip_check_mc_rcu(). This attempts to acquire &amp;im-&gt;lock while &amp;pmc-&gt;lock
is already held on the same CPU, triggering a lockdep recursive locking
warning / deadlock.</p>
<p>Fix this by converting IPv4 struct ip_sf_list to RCU, mirroring the
IPv6 implementation in net/ipv6/mcast.c:</p>
<p>1. Add struct rcu_head to struct ip_sf_list and annotate sf_next,
   sources, and tomb as __rcu pointers.
2. Use rcu_assign_pointer() and kfree_rcu() for list updates and
   deletions.
3. Remove spin_lock_bh(&amp;im-&gt;lock) from ip_check_mc_rcu() and traverse
   im-&gt;sources locklessly with for_each_psf_rcu(), reading and writing
   counter fields with READ_ONCE() and WRITE_ONCE().</p>
<p>Note: RCU conversion of /proc/net/mcfilter will be done in a
separate patch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-98103"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-2hrc-mwqg-6fr2</id>
    <title>GHSA-2hrc-mwqg-6fr2</title>
    <updated>2026-09-28T16:55:18.634895+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>igmp: convert struct ip_sf_list to RCU</p>
<p>Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu")
added spin_lock_bh(&amp;im-&gt;lock) to ip_check_mc_rcu() to prevent a
use-after-free while iterating im-&gt;sources during concurrent deletions.</p>
<p>However, ip_check_mc_rcu() is called from RCU read-side critical
sections in packet receive and route lookup fast paths (e.g.
__mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()).</p>
<p>When igmpv3_send_cr() or igmpv3_send_report() holds &amp;pmc-&gt;lock and
calls add_grec() -&gt; igmpv3_newpack() -&gt; ip_route_output_ports(),
an XFRM policy matching a multicast destination triggers
xfrm_tmpl_resolve_one() -&gt; xfrm4_get_saddr() -&gt; __mkroute_output() -&gt;
ip_check_mc_rcu(). This attempts to acquire &amp;im-&gt;lock while &amp;pmc-&gt;lock
is already held on the same CPU, triggering a lockdep recursive locking
warning / deadlock.</p>
<p>Fix this by converting IPv4 struct ip_sf_list to RCU, mirroring the
IPv6 implementation in net/ipv6/mcast.c:</p>
<p>1. Add struct rcu_head to struct ip_sf_list and annotate sf_next,
   sources, and tomb as __rcu pointers.
2. Use rcu_assign_pointer() and kfree_rcu() for list updates and
   deletions.
3. Remove spin_lock_bh(&amp;im-&gt;lock) from ip_check_mc_rcu() and traverse
   im-&gt;sources locklessly with for_each_psf_rcu(), reading and writing
   counter fields with READ_ONCE() and WRITE_ONCE().</p>
<p>Note: RCU conversion of /proc/net/mcfilter will be done in a
separate patch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-2hrc-mwqg-6fr2"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98103</id>
    <title>UBUNTU-CVE-2026-98103</title>
    <updated>2026-09-28T16:55:18.634976+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>In the Linux kernel, the following vulnerability has been resolved: igmp: convert struct ip_sf_list to RCU Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu") added spin_lock_bh(&amp;im-&gt;lock) to ip_check_mc_rcu() to prevent a use-after-free while iterating im-&gt;sources during concurrent deletions. However, ip_check_mc_rcu() is called from RCU read-side critical sections in packet receive and route lookup fast paths (e.g. __mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()). When igmpv3_send_cr() or igmpv3_send_report() holds &amp;pmc-&gt;lock and calls add_grec() -&gt; igmpv3_newpack() -&gt; ip_route_output_ports(), an XFRM policy matching a multicast destination triggers xfrm_tmpl_resolve_one() -&gt; xfrm4_get_saddr() -&gt; __mkroute_output() -&gt; ip_check_mc_rcu(). This attempts to acquire &amp;im-&gt;lock while &amp;pmc-&gt;lock is already held on the same CPU, triggering a lockdep recursive locking warning / deadlock. Fix this by converting IPv4 struct ip_sf_list to RCU, mirroring the IPv6 implementation in net/ipv6/mcast.c: 1. Add struct rcu_head to struct ip_sf_list and annotate sf_next,    sources, and tomb as __rcu pointers. 2. Use rcu_assign_pointer() and kfree_rcu() for list updates and    deletions. 3. Remove spin_lock_bh(&amp;im-&gt;lock) from ip_check_mc_rcu() and traverse    im-&gt;sources locklessly with for_each_psf_rcu(), reading and writing    counter fields with READ_ONCE() and WRITE_ONCE(). Note: RCU conversion of /proc/net/mcfilter will be done in a separate patch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98103"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</id>
    <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-09-28T16:55:18.635862+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579"/>
  </entry>
</feed>
