<?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:56:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56650</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56650</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-56650</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0133 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0133</link>
      <description>certfr-2025-avi-0133</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0133</guid>
    </item>
    <item>
      <title>OESA-2025-1161 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1161</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;amp;quot;use after free&amp;amp;quot; error was
caught by KASAN at this line - &amp;amp;apos;ceph_buffer_get(arg-&amp;amp;gt;xattr_buf);&amp;amp;apos;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;amp;quot;handle_cap_grant()&amp;amp;quot; refcount is decremented by this
line - &amp;amp;apos;ceph_buffer_put(ci-&amp;amp;gt;i_xattrs.blob);&amp;amp;apos;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;amp;gt;xattr_buf is assigned to ci-&amp;amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;amp;quot;use after free&amp;amp;quot; error.(CVE-2024-26689)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;amp;gt;= map-&amp;amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;amp;quot;use after free&amp;amp;quot; error was
caught by KASAN at this line - &amp;amp;apos;ceph_buffer_get(arg-&amp;amp;gt;xattr_buf);&amp;amp;apos;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;amp;quot;handle_cap_grant()&amp;amp;quot; refcount is decremented by this
line - &amp;amp;apos;ceph_buffer_put(ci-&amp;amp;gt;i_xattrs.blob);&amp;amp;apos;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;amp;gt;xattr_buf is assigned to ci-&amp;amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;amp;quot;use after free&amp;amp;quot; error.(CVE-2024-26689)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;amp;gt;= map-&amp;amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1161</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56650</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56650</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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: fix LED ID check in led_tg_check() Syzbot has reported the following BUG detected by KASAN: BUG: KASAN: slab-out-of-bounds in strlen+0x58/0x70 Read of size 1 at addr ffff8881022da0c8 by task repro/5879 ... Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0x241/0x360  ? __pfx_dump_stack_lvl+0x10/0x10  ? __pfx__printk+0x10/0x10  ? _printk+0xd5/0x120  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x183/0x530  print_report+0x169/0x550  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x45f/0x530  ? __phys_addr+0xba/0x170  ? strlen+0x58/0x70  kasan_report+0x143/0x180  ? strlen+0x58/0x70  strlen+0x58/0x70  kstrdup+0x20/0x80  led_tg_check+0x18b/0x3c0  xt_check_target+0x3bb/0xa40  ? __pfx_xt_check_target+0x10/0x10  ? stack_depot_save_flags+0x6e4/0x830  ? nft_target_init+0x174/0xc30  nft_target_init+0x82d/0xc30  ? __pfx_nft_target_init+0x10/0x10  ? nf_tables_newrule+0x1609/0x2980  ? nf_tables_newrule+0x1609/0x2980  ? rcu_is_watching+0x15/0xb0  ? nf_tables_newrule+0x1609/0x2980  ? nf_tables_newrule+0x1609/0x2980  ? __kmalloc_noprof+0x21a/0x400  nf_tables_newrule+0x1860/0x2980  ? __pfx_nf_tables_newrule+0x10/0x10  ? __nla_parse+0x40/0x60  nfnetlink_rcv+0x14e5/0x2ab0  ? __pfx_validate_chain+0x10/0x10  ? __pfx_nfnetlink_rcv+0x10/0x10  ? __lock_acquire+0x1384/0x2050  ? netlink_deliver_tap+0x2e/0x1b0  ? __pfx_lock_release+0x10/0x10  ? netlink_deliver_tap+0x2e/0x1b0  netli…&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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: fix LED ID check in led_tg_check() Syzbot has reported the following BUG detected by KASAN: BUG: KASAN: slab-out-of-bounds in strlen+0x58/0x70 Read of size 1 at addr ffff8881022da0c8 by task repro/5879 ... Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0x241/0x360  ? __pfx_dump_stack_lvl+0x10/0x10  ? __pfx__printk+0x10/0x10  ? _printk+0xd5/0x120  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x183/0x530  print_report+0x169/0x550  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x183/0x530  ? __virt_addr_valid+0x45f/0x530  ? __phys_addr+0xba/0x170  ? strlen+0x58/0x70  kasan_report+0x143/0x180  ? strlen+0x58/0x70  strlen+0x58/0x70  kstrdup+0x20/0x80  led_tg_check+0x18b/0x3c0  xt_check_target+0x3bb/0xa40  ? __pfx_xt_check_target+0x10/0x10  ? stack_depot_save_flags+0x6e4/0x830  ? nft_target_init+0x174/0xc30  nft_target_init+0x82d/0xc30  ? __pfx_nft_target_init+0x10/0x10  ? nf_tables_newrule+0x1609/0x2980  ? nf_tables_newrule+0x1609/0x2980  ? rcu_is_watching+0x15/0xb0  ? nf_tables_newrule+0x1609/0x2980  ? nf_tables_newrule+0x1609/0x2980  ? __kmalloc_noprof+0x21a/0x400  nf_tables_newrule+0x1860/0x2980  ? __pfx_nf_tables_newrule+0x10/0x10  ? __nla_parse+0x40/0x60  nfnetlink_rcv+0x14e5/0x2ab0  ? __pfx_validate_chain+0x10/0x10  ? __pfx_nfnetlink_rcv+0x10/0x10  ? __lock_acquire+0x1384/0x2050  ? netlink_deliver_tap+0x2e/0x1b0  ? __pfx_lock_release+0x10/0x10  ? netlink_deliver_tap+0x2e/0x1b0  netli…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56650</guid>
    </item>
  </channel>
</rss>
