<?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 15:07:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89508</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89508</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-89508</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>OESA-2026-4185 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4185</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: ipset: fix race between dump and ip_set_list resize&lt;/p&gt;
&lt;p&gt;The release path of ip_set_dump_do() and ip_set_dump_done() read
inst-&amp;amp;gt;ip_set_list via ip_set_ref_netlink(), a plain rcu_dereference_raw()
of the array pointer. These run from netlink_recvmsg() without the nfnl
mutex and without an RCU read-side critical section.&lt;/p&gt;
&lt;p&gt;A concurrent ip_set_create() can grow the array: it publishes the new
array, calls synchronize_net() and then kvfree()s the old one. Since the
dump paths read the array outside any RCU reader, synchronize_net() does
not wait for them and the old array can be freed while they still index
into it, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;The dumped set itself stays pinned via set-&amp;amp;gt;ref_netlink, so only the
array load needs protecting. Take rcu_read_lock() around it, matching
ip_set_get_byname() and __ip_set_put_byindex().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697)
  Read of size 8 at addr ffff88800b5c4018 by task exploit/150
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697)
   netlink_dump (net/netlink/af_netlink.c:2325)
   netlink_recvmsg (net/netlink/af_netlink.c:1976)
   sock_recvmsg (net/socket.c:1159)
   __sys_recvfrom (net/socket.c:2315)
   ...
  Oops: general protection fault, probably for non-can…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: ipset: fix race between dump and ip_set_list resize&lt;/p&gt;
&lt;p&gt;The release path of ip_set_dump_do() and ip_set_dump_done() read
inst-&amp;amp;gt;ip_set_list via ip_set_ref_netlink(), a plain rcu_dereference_raw()
of the array pointer. These run from netlink_recvmsg() without the nfnl
mutex and without an RCU read-side critical section.&lt;/p&gt;
&lt;p&gt;A concurrent ip_set_create() can grow the array: it publishes the new
array, calls synchronize_net() and then kvfree()s the old one. Since the
dump paths read the array outside any RCU reader, synchronize_net() does
not wait for them and the old array can be freed while they still index
into it, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;The dumped set itself stays pinned via set-&amp;amp;gt;ref_netlink, so only the
array load needs protecting. Take rcu_read_lock() around it, matching
ip_set_get_byname() and __ip_set_put_byindex().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697)
  Read of size 8 at addr ffff88800b5c4018 by task exploit/150
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697)
   netlink_dump (net/netlink/af_netlink.c:2325)
   netlink_recvmsg (net/netlink/af_netlink.c:1976)
   sock_recvmsg (net/socket.c:1159)
   __sys_recvfrom (net/socket.c:2315)
   ...
  Oops: general protection fault, probably for non-can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4185</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89508</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89508</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 238 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/ucma: Lock the handler in ucma_set_ib_path() ucma_set_ib_path() calls ucma_event_handler() straight from the write() path, without the handler lock that keeps ctx-&amp;gt;file stable while a uevent is queued.  The handler re-reads ctx-&amp;gt;file for every dereference: 	mutex_lock(&amp;amp;ctx-&amp;gt;file-&amp;gt;mut);			/* file A */ 	list_add_tail(&amp;amp;uevent-&amp;gt;list, &amp;amp;ctx-&amp;gt;file-&amp;gt;event_list);	/* file B */ 	mutex_unlock(&amp;amp;ctx-&amp;gt;file-&amp;gt;mut);			/* file B */ 	wake_up_interruptible(&amp;amp;ctx-&amp;gt;file-&amp;gt;poll_wait);	/* file B */ A concurrent ucma_migrate_id() reassigns ctx-&amp;gt;file while the SET_OPTION caller sleeps in mutex_lock(), so the list_add_tail() lands on file B&amp;#39;s event_list while only file A&amp;#39;s mutex is held, racing every other user of that list:   BUG: KASAN: slab-use-after-free in __list_add_valid_or_report+0x1aa/0x1c0   Read of size 8 at addr ffff888153c6a418 by task poc_corr/486   Call Trace:    __list_add_valid_or_report+0x1aa/0x1c0    ucma_event_handler+0x1be/0xc00    ucma_set_ib_path+0x45e/0x710    ucma_set_option+0x32e/0x590    ucma_write+0x1f9/0x330   Allocated by task 505:    ucma_write_cm_event+0x1a1/0x660   Freed by task 505:    kfree+0x1da/0x4c0    ucma_get_event+0x5d5/0x7e0 The freed object is a ucma_event that another thread dequeued from file B&amp;#39;s list under file B&amp;#39;s mutex.  File A&amp;#39;s mut is left held on top of that, wedging its next writer in uninterruptible sleep. This path needs a bound and address-resolved cm_id, so it requires an RDMA…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 238 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/ucma: Lock the handler in ucma_set_ib_path() ucma_set_ib_path() calls ucma_event_handler() straight from the write() path, without the handler lock that keeps ctx-&amp;gt;file stable while a uevent is queued.  The handler re-reads ctx-&amp;gt;file for every dereference: 	mutex_lock(&amp;amp;ctx-&amp;gt;file-&amp;gt;mut);			/* file A */ 	list_add_tail(&amp;amp;uevent-&amp;gt;list, &amp;amp;ctx-&amp;gt;file-&amp;gt;event_list);	/* file B */ 	mutex_unlock(&amp;amp;ctx-&amp;gt;file-&amp;gt;mut);			/* file B */ 	wake_up_interruptible(&amp;amp;ctx-&amp;gt;file-&amp;gt;poll_wait);	/* file B */ A concurrent ucma_migrate_id() reassigns ctx-&amp;gt;file while the SET_OPTION caller sleeps in mutex_lock(), so the list_add_tail() lands on file B&amp;#39;s event_list while only file A&amp;#39;s mutex is held, racing every other user of that list:   BUG: KASAN: slab-use-after-free in __list_add_valid_or_report+0x1aa/0x1c0   Read of size 8 at addr ffff888153c6a418 by task poc_corr/486   Call Trace:    __list_add_valid_or_report+0x1aa/0x1c0    ucma_event_handler+0x1be/0xc00    ucma_set_ib_path+0x45e/0x710    ucma_set_option+0x32e/0x590    ucma_write+0x1f9/0x330   Allocated by task 505:    ucma_write_cm_event+0x1a1/0x660   Freed by task 505:    kfree+0x1da/0x4c0    ucma_get_event+0x5d5/0x7e0 The freed object is a ucma_event that another thread dequeued from file B&amp;#39;s list under file B&amp;#39;s mutex.  File A&amp;#39;s mut is left held on top of that, wedging its next writer in uninterruptible sleep. This path needs a bound and address-resolved cm_id, so it requires an RDMA…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89508</guid>
    </item>
  </channel>
</rss>
