<?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 05:59:31 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39683</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39683</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-2025-39683</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — 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-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>OESA-2025-2465 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2465</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2465</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39683</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39683</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 200 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser-&amp;gt;buffer when trace_get_user failed When the length of the string written to set_ftrace_filter exceeds FTRACE_BUFF_MAX, the following KASAN alarm will be triggered: BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0 Read of size 1 at addr ffff0000d00bd5ba by task ash/165 CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty Hardware name: linux,dummy-virt (DT) Call trace:  show_stack+0x34/0x50 (C)  dump_stack_lvl+0xa0/0x158  print_address_description.constprop.0+0x88/0x398  print_report+0xb0/0x280  kasan_report+0xa4/0xf0  __asan_report_load1_noabort+0x20/0x30  strsep+0x18c/0x1b0  ftrace_process_regex.isra.0+0x100/0x2d8  ftrace_regex_release+0x484/0x618  __fput+0x364/0xa58  ____fput+0x28/0x40  task_work_run+0x154/0x278  do_notify_resume+0x1f0/0x220  el0_svc+0xec/0xf0  el0t_64_sync_handler+0xa0/0xe8  el0t_64_sync+0x1ac/0x1b0 The reason is that trace_get_user will fail when processing a string longer than FTRACE_BUFF_MAX, but not set the end of parser-&amp;gt;buffer to 0. Then an OOB access will be triggered in ftrace_regex_release-&amp;gt; ftrace_process_regex-&amp;gt;strsep-&amp;gt;strpbrk. We can solve this problem by limiting access to parser-&amp;gt;buffer when trace_get_user failed.&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 200 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser-&amp;gt;buffer when trace_get_user failed When the length of the string written to set_ftrace_filter exceeds FTRACE_BUFF_MAX, the following KASAN alarm will be triggered: BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0 Read of size 1 at addr ffff0000d00bd5ba by task ash/165 CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty Hardware name: linux,dummy-virt (DT) Call trace:  show_stack+0x34/0x50 (C)  dump_stack_lvl+0xa0/0x158  print_address_description.constprop.0+0x88/0x398  print_report+0xb0/0x280  kasan_report+0xa4/0xf0  __asan_report_load1_noabort+0x20/0x30  strsep+0x18c/0x1b0  ftrace_process_regex.isra.0+0x100/0x2d8  ftrace_regex_release+0x484/0x618  __fput+0x364/0xa58  ____fput+0x28/0x40  task_work_run+0x154/0x278  do_notify_resume+0x1f0/0x220  el0_svc+0xec/0xf0  el0t_64_sync_handler+0xa0/0xe8  el0t_64_sync+0x1ac/0x1b0 The reason is that trace_get_user will fail when processing a string longer than FTRACE_BUFF_MAX, but not set the end of parser-&amp;gt;buffer to 0. Then an OOB access will be triggered in ftrace_regex_release-&amp;gt; ftrace_process_regex-&amp;gt;strsep-&amp;gt;strpbrk. We can solve this problem by limiting access to parser-&amp;gt;buffer when trace_get_user failed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39683</guid>
    </item>
  </channel>
</rss>
