<?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>Sat, 03 Oct 2026 09:56:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72493</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-72493</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-72493</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72493</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: serialize netif_running() check in enqueue_to_backlog()&lt;/p&gt;
&lt;p&gt;Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().&lt;/p&gt;
&lt;p&gt;The root cause is a race condition where packets can escape the backlog
flushing during device unregistration (e.g., during netns exit).&lt;/p&gt;
&lt;p&gt;Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;)
introduced a lockless netif_running() check in enqueue_to_backlog() to
prevent queuing packets to an unregistering device.&lt;/p&gt;
&lt;p&gt;However, this creates a TOCTOU race window.&lt;/p&gt;
&lt;p&gt;A lockless transmitter (like veth_xmit) can pass
the check before dev_close() clears IFF_UP. If the transmitter is then
delayed, flush_all_backlogs() can run and finish before the transmitter
grabs the backlog lock and queues the packet. The packet then escapes
the flush and triggers UAF later when processed.&lt;/p&gt;
&lt;p&gt;Fix this by moving the netif_running() check inside the backlog lock.
This serializes the check with the flush work (which also grabs the lock).
We then either queue the packet before the flush runs (so it gets flushed),
or check netif_running() after the flush/close completes (so it gets dropped).&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;net: serialize netif_running() check in enqueue_to_backlog()&lt;/p&gt;
&lt;p&gt;Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().&lt;/p&gt;
&lt;p&gt;The root cause is a race condition where packets can escape the backlog
flushing during device unregistration (e.g., during netns exit).&lt;/p&gt;
&lt;p&gt;Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;)
introduced a lockless netif_running() check in enqueue_to_backlog() to
prevent queuing packets to an unregistering device.&lt;/p&gt;
&lt;p&gt;However, this creates a TOCTOU race window.&lt;/p&gt;
&lt;p&gt;A lockless transmitter (like veth_xmit) can pass
the check before dev_close() clears IFF_UP. If the transmitter is then
delayed, flush_all_backlogs() can run and finish before the transmitter
grabs the backlog lock and queues the packet. The packet then escapes
the flush and triggers UAF later when processed.&lt;/p&gt;
&lt;p&gt;Fix this by moving the netif_running() check inside the backlog lock.
This serializes the check with the flush work (which also grabs the lock).
We then either queue the packet before the flush runs (so it gets flushed),
or check netif_running() after the flush/close completes (so it gets dropped).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72493</guid>
    </item>
    <item>
      <title>GHSA-hhj5-7x2f-mw3r</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hhj5-7x2f-mw3r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: serialize netif_running() check in enqueue_to_backlog()&lt;/p&gt;
&lt;p&gt;Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().&lt;/p&gt;
&lt;p&gt;The root cause is a race condition where packets can escape the backlog
flushing during device unregistration (e.g., during netns exit).&lt;/p&gt;
&lt;p&gt;Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;)
introduced a lockless netif_running() check in enqueue_to_backlog() to
prevent queuing packets to an unregistering device.&lt;/p&gt;
&lt;p&gt;However, this creates a TOCTOU race window.&lt;/p&gt;
&lt;p&gt;A lockless transmitter (like veth_xmit) can pass
the check before dev_close() clears IFF_UP. If the transmitter is then
delayed, flush_all_backlogs() can run and finish before the transmitter
grabs the backlog lock and queues the packet. The packet then escapes
the flush and triggers UAF later when processed.&lt;/p&gt;
&lt;p&gt;Fix this by moving the netif_running() check inside the backlog lock.
This serializes the check with the flush work (which also grabs the lock).
We then either queue the packet before the flush runs (so it gets flushed),
or check netif_running() after the flush/close completes (so it gets dropped).&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;net: serialize netif_running() check in enqueue_to_backlog()&lt;/p&gt;
&lt;p&gt;Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().&lt;/p&gt;
&lt;p&gt;The root cause is a race condition where packets can escape the backlog
flushing during device unregistration (e.g., during netns exit).&lt;/p&gt;
&lt;p&gt;Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;)
introduced a lockless netif_running() check in enqueue_to_backlog() to
prevent queuing packets to an unregistering device.&lt;/p&gt;
&lt;p&gt;However, this creates a TOCTOU race window.&lt;/p&gt;
&lt;p&gt;A lockless transmitter (like veth_xmit) can pass
the check before dev_close() clears IFF_UP. If the transmitter is then
delayed, flush_all_backlogs() can run and finish before the transmitter
grabs the backlog lock and queues the packet. The packet then escapes
the flush and triggers UAF later when processed.&lt;/p&gt;
&lt;p&gt;Fix this by moving the netif_running() check inside the backlog lock.
This serializes the check with the flush work (which also grabs the lock).
We then either queue the packet before the flush runs (so it gets flushed),
or check netif_running() after the flush/close completes (so it gets dropped).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hhj5-7x2f-mw3r</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-72493 — net: serialize netif_running() check in enqueue_to_backlog()</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-72493</link>
      <description>msrc_CVE-2026-72493</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-72493</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72493</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72493</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: net: serialize netif_running() check in enqueue_to_backlog() Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup(). The root cause is a race condition where packets can escape the backlog flushing during device unregistration (e.g., during netns exit). Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;) introduced a lockless netif_running() check in enqueue_to_backlog() to prevent queuing packets to an unregistering device. However, this creates a TOCTOU race window. A lockless transmitter (like veth_xmit) can pass the check before dev_close() clears IFF_UP. If the transmitter is then delayed, flush_all_backlogs() can run and finish before the transmitter grabs the backlog lock and queues the packet. The packet then escapes the flush and triggers UAF later when processed. Fix this by moving the netif_running() check inside the backlog lock. This serializes the check with the flush work (which also grabs the lock). We then either queue the packet before the flush runs (so it gets flushed), or check netif_running() after the flush/close completes (so it gets dropped).&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: net: serialize netif_running() check in enqueue_to_backlog() Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup(). The root cause is a race condition where packets can escape the backlog flushing during device unregistration (e.g., during netns exit). Commit e9e4dd3267d0 (&amp;#34;net: do not process device backlog during unregistration&amp;#34;) introduced a lockless netif_running() check in enqueue_to_backlog() to prevent queuing packets to an unregistering device. However, this creates a TOCTOU race window. A lockless transmitter (like veth_xmit) can pass the check before dev_close() clears IFF_UP. If the transmitter is then delayed, flush_all_backlogs() can run and finish before the transmitter grabs the backlog lock and queues the packet. The packet then escapes the flush and triggers UAF later when processed. Fix this by moving the netif_running() check inside the backlog lock. This serializes the check with the flush work (which also grabs the lock). We then either queue the packet before the flush runs (so it gets flushed), or check netif_running() after the flush/close completes (so it gets dropped).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72493</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>
