<?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 02:11:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-53156</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-53156</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-53156</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0047 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0047</link>
      <description>certfr-2025-avi-0047</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0047</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-53156</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-53156</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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() I found the following bug in my fuzzer:   UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath9k/htc_hst.c:26:51   index 255 is out of range for type &amp;#39;htc_endpoint [22]&amp;#39;   CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.11.0-rc6-dirty #14   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014   Workqueue: events request_firmware_work_func   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x180/0x1b0    __ubsan_handle_out_of_bounds+0xd4/0x130    htc_issue_send.constprop.0+0x20c/0x230    ? _raw_spin_unlock_irqrestore+0x3c/0x70    ath9k_wmi_cmd+0x41d/0x610    ? mark_held_locks+0x9f/0xe0    ... Since this bug has been confirmed to be caused by insufficient verification of conn_rsp_epid, I think it would be appropriate to add a range check for conn_rsp_epid to htc_connect_service() to prevent the bug from occurring.&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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() I found the following bug in my fuzzer:   UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath9k/htc_hst.c:26:51   index 255 is out of range for type &amp;#39;htc_endpoint [22]&amp;#39;   CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.11.0-rc6-dirty #14   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014   Workqueue: events request_firmware_work_func   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x180/0x1b0    __ubsan_handle_out_of_bounds+0xd4/0x130    htc_issue_send.constprop.0+0x20c/0x230    ? _raw_spin_unlock_irqrestore+0x3c/0x70    ath9k_wmi_cmd+0x41d/0x610    ? mark_held_locks+0x9f/0xe0    ... Since this bug has been confirmed to be caused by insufficient verification of conn_rsp_epid, I think it would be appropriate to add a range check for conn_rsp_epid to htc_connect_service() to prevent the bug from occurring.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-53156</guid>
    </item>
  </channel>
</rss>
