<?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 03:47:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-49569</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-49569</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-2024-49569</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>OESA-2025-1158 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1158</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;ila: call nf_unregister_net_hooks() sooner&lt;/p&gt;
&lt;p&gt;syzbot found an use-after-free Read in ila_nf_input [1]&lt;/p&gt;
&lt;p&gt;Issue here is that ila_xlat_exit_net() frees the rhashtable,
then call nf_unregister_net_hooks().&lt;/p&gt;
&lt;p&gt;It should be done in the reverse way, with a synchronize_rcu().&lt;/p&gt;
&lt;p&gt;This is a good match for a pre_exit() method.&lt;/p&gt;
&lt;p&gt;[1]
 BUG: KASAN: use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline]
 BUG: KASAN: use-after-free in __rhashtable_lookup include/linux/rhashtable.h:604 [inline]
 BUG: KASAN: use-after-free in rhashtable_lookup include/linux/rhashtable.h:646 [inline]
 BUG: KASAN: use-after-free in rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672
Read of size 4 at addr ffff888064620008 by task ksoftirqd/0/16&lt;/p&gt;
&lt;p&gt;CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc4-syzkaller-00238-g2ad6d23f465a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
  __dump_stack lib/dump_stack.c:93 [inline]
  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
  print_address_description mm/kasan/report.c:377 [inline]
  print_report+0x169/0x550 mm/kasan/report.c:488
  kasan_report+0x143/0x180 mm/kasan/report.c:601
  rht_key_hashfn include/linux/rhashtable.h:159 [inline]
  __rhashtable_lookup include/linux/rhashtable.h:604 [inline]
  rhashtable_lookup include/lin…&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;ila: call nf_unregister_net_hooks() sooner&lt;/p&gt;
&lt;p&gt;syzbot found an use-after-free Read in ila_nf_input [1]&lt;/p&gt;
&lt;p&gt;Issue here is that ila_xlat_exit_net() frees the rhashtable,
then call nf_unregister_net_hooks().&lt;/p&gt;
&lt;p&gt;It should be done in the reverse way, with a synchronize_rcu().&lt;/p&gt;
&lt;p&gt;This is a good match for a pre_exit() method.&lt;/p&gt;
&lt;p&gt;[1]
 BUG: KASAN: use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline]
 BUG: KASAN: use-after-free in __rhashtable_lookup include/linux/rhashtable.h:604 [inline]
 BUG: KASAN: use-after-free in rhashtable_lookup include/linux/rhashtable.h:646 [inline]
 BUG: KASAN: use-after-free in rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672
Read of size 4 at addr ffff888064620008 by task ksoftirqd/0/16&lt;/p&gt;
&lt;p&gt;CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc4-syzkaller-00238-g2ad6d23f465a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
  __dump_stack lib/dump_stack.c:93 [inline]
  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
  print_address_description mm/kasan/report.c:377 [inline]
  print_report+0x169/0x550 mm/kasan/report.c:488
  kasan_report+0x143/0x180 mm/kasan/report.c:601
  rht_key_hashfn include/linux/rhashtable.h:159 [inline]
  __rhashtable_lookup include/linux/rhashtable.h:604 [inline]
  rhashtable_lookup include/lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1158</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-49569</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49569</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 166 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: unquiesce admin_q before destroy it Kernel will hang on destroy admin_q while we create ctrl failed, such as following calltrace: PID: 23644    TASK: ff2d52b40f439fc0  CPU: 2    COMMAND: &amp;#34;nvme&amp;#34;  #0 [ff61d23de260fb78] __schedule at ffffffff8323bc15  #1 [ff61d23de260fc08] schedule at ffffffff8323c014  #2 [ff61d23de260fc28] blk_mq_freeze_queue_wait at ffffffff82a3dba1  #3 [ff61d23de260fc78] blk_freeze_queue at ffffffff82a4113a  #4 [ff61d23de260fc90] blk_cleanup_queue at ffffffff82a33006  #5 [ff61d23de260fcb0] nvme_rdma_destroy_admin_queue at ffffffffc12686ce  #6 [ff61d23de260fcc8] nvme_rdma_setup_ctrl at ffffffffc1268ced  #7 [ff61d23de260fd28] nvme_rdma_create_ctrl at ffffffffc126919b  #8 [ff61d23de260fd68] nvmf_dev_write at ffffffffc024f362  #9 [ff61d23de260fe38] vfs_write at ffffffff827d5f25     RIP: 00007fda7891d574  RSP: 00007ffe2ef06958  RFLAGS: 00000202     RAX: ffffffffffffffda  RBX: 000055e8122a4d90  RCX: 00007fda7891d574     RDX: 000000000000012b  RSI: 000055e8122a4d90  RDI: 0000000000000004     RBP: 00007ffe2ef079c0   R8: 000000000000012b   R9: 000055e8122a4d90     R10: 0000000000000000  R11: 0000000000000202  R12: 0000000000000004     R13: 000055e8122923c0  R14: 000000000000012b  R15: 00007fda78a54500     ORIG_RAX: 0000000000000001  CS: 0033  SS: 002b This due to we have quiesced admi_q before cancel requests, but forgot to unquiesce before destroy it, as a result we fail to drain the pend…&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 166 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: unquiesce admin_q before destroy it Kernel will hang on destroy admin_q while we create ctrl failed, such as following calltrace: PID: 23644    TASK: ff2d52b40f439fc0  CPU: 2    COMMAND: &amp;#34;nvme&amp;#34;  #0 [ff61d23de260fb78] __schedule at ffffffff8323bc15  #1 [ff61d23de260fc08] schedule at ffffffff8323c014  #2 [ff61d23de260fc28] blk_mq_freeze_queue_wait at ffffffff82a3dba1  #3 [ff61d23de260fc78] blk_freeze_queue at ffffffff82a4113a  #4 [ff61d23de260fc90] blk_cleanup_queue at ffffffff82a33006  #5 [ff61d23de260fcb0] nvme_rdma_destroy_admin_queue at ffffffffc12686ce  #6 [ff61d23de260fcc8] nvme_rdma_setup_ctrl at ffffffffc1268ced  #7 [ff61d23de260fd28] nvme_rdma_create_ctrl at ffffffffc126919b  #8 [ff61d23de260fd68] nvmf_dev_write at ffffffffc024f362  #9 [ff61d23de260fe38] vfs_write at ffffffff827d5f25     RIP: 00007fda7891d574  RSP: 00007ffe2ef06958  RFLAGS: 00000202     RAX: ffffffffffffffda  RBX: 000055e8122a4d90  RCX: 00007fda7891d574     RDX: 000000000000012b  RSI: 000055e8122a4d90  RDI: 0000000000000004     RBP: 00007ffe2ef079c0   R8: 000000000000012b   R9: 000055e8122a4d90     R10: 0000000000000000  R11: 0000000000000202  R12: 0000000000000004     R13: 000055e8122923c0  R14: 000000000000012b  R15: 00007fda78a54500     ORIG_RAX: 0000000000000001  CS: 0033  SS: 002b This due to we have quiesced admi_q before cancel requests, but forgot to unquiesce before destroy it, as a result we fail to drain the pend…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49569</guid>
    </item>
  </channel>
</rss>
