<?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 01:20:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-46782</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-46782</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-46782</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — 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-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>OESA-2024-2325 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2325</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2325</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46782</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46782</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ila: call nf_unregister_net_hooks() sooner syzbot found an use-after-free Read in ila_nf_input [1] Issue here is that ila_xlat_exit_net() frees the rhashtable, then call nf_unregister_net_hooks(). It should be done in the reverse way, with a synchronize_rcu(). This is a good match for a pre_exit() method. [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 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;lt;TASK&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/linux/rhashtable.h:646 [inline]   rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashta…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ila: call nf_unregister_net_hooks() sooner syzbot found an use-after-free Read in ila_nf_input [1] Issue here is that ila_xlat_exit_net() frees the rhashtable, then call nf_unregister_net_hooks(). It should be done in the reverse way, with a synchronize_rcu(). This is a good match for a pre_exit() method. [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 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;lt;TASK&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/linux/rhashtable.h:646 [inline]   rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashta…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-46782</guid>
    </item>
  </channel>
</rss>
