<?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://127.0.0.1:10001</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, 21 Nov 2026 14:27:59 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74700</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74700</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://127.0.0.1:10001/vuln/bell-cve-2026-74700</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74700</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74700</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers Another challenge with unlocked filters. There is a short window in tc_new_tfilter where a tcf_proto can be found and briefly referenced by a totally unrelated, unlocked classifier&amp;#39;s request and cause a race. Feng created a poc which created this race with two threads, one creating a u32 filter and other a flower filter in the same chain/prio: 1. Both threads enter tc_new_tfilter, both find the chain empty, both    drop filter_chain_lock 2. u32 finishes tcf_proto_create(&amp;#34;u32&amp;#34;) first, calls    tcf_chain_tp_insert_unique() -&amp;gt; inserts u32_tp into the chain 3. flower finishes tcf_proto_create(&amp;#34;flower&amp;#34;) later, calls    tcf_chain_tp_insert_unique() -&amp;gt; tcf_chain_tp_find() now sees u32_tp    already there, takes a reference on it, destroys flower&amp;#39;s own tp_new    and returns u32_tp to the caller. Flower then hits the kind mismatch check (because it requested for kind &amp;#34;flower&amp;#34; but tp-&amp;gt;ops-&amp;gt;kind is &amp;#34;u32&amp;#34;) and goes through the errout path which calls tcf_proto_put() on u32_tp. If the u32 thread has already gone through its own errout (its change() call failed on the PoC&amp;#39;s empty options) and dropped its create and insert refs, flower&amp;#39;s put is the last one and drops u32_tp&amp;#39;s refcnt to zero. At this point tp-&amp;gt;ops-&amp;gt;destroy() runs in a context that never took rtnl_lock. When that happens, it might cause a UAF like the following (illustrated by th…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers Another challenge with unlocked filters. There is a short window in tc_new_tfilter where a tcf_proto can be found and briefly referenced by a totally unrelated, unlocked classifier&amp;#39;s request and cause a race. Feng created a poc which created this race with two threads, one creating a u32 filter and other a flower filter in the same chain/prio: 1. Both threads enter tc_new_tfilter, both find the chain empty, both    drop filter_chain_lock 2. u32 finishes tcf_proto_create(&amp;#34;u32&amp;#34;) first, calls    tcf_chain_tp_insert_unique() -&amp;gt; inserts u32_tp into the chain 3. flower finishes tcf_proto_create(&amp;#34;flower&amp;#34;) later, calls    tcf_chain_tp_insert_unique() -&amp;gt; tcf_chain_tp_find() now sees u32_tp    already there, takes a reference on it, destroys flower&amp;#39;s own tp_new    and returns u32_tp to the caller. Flower then hits the kind mismatch check (because it requested for kind &amp;#34;flower&amp;#34; but tp-&amp;gt;ops-&amp;gt;kind is &amp;#34;u32&amp;#34;) and goes through the errout path which calls tcf_proto_put() on u32_tp. If the u32 thread has already gone through its own errout (its change() call failed on the PoC&amp;#39;s empty options) and dropped its create and insert refs, flower&amp;#39;s put is the last one and drops u32_tp&amp;#39;s refcnt to zero. At this point tp-&amp;gt;ops-&amp;gt;destroy() runs in a context that never took rtnl_lock. When that happens, it might cause a UAF like the following (illustrated by th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74700</guid>
    </item>
  </channel>
</rss>
