<?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 06:03:53 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-39474</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-39474</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-39474</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — 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-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2025-1097 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1097</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;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&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;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1097</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-39474</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39474</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL commit a421ef303008 (&amp;#34;mm: allow !GFP_KERNEL allocations for kvmalloc&amp;#34;) includes support for __GFP_NOFAIL, but it presents a conflict with commit dd544141b9eb (&amp;#34;vmalloc: back off when the current task is OOM-killed&amp;#34;).  A possible scenario is as follows: process-a __vmalloc_node_range(GFP_KERNEL | __GFP_NOFAIL)     __vmalloc_area_node()         vm_area_alloc_pages() 		--&amp;gt; oom-killer send SIGKILL to process-a         if (fatal_signal_pending(current)) break; --&amp;gt; return NULL; To fix this, do not check fatal_signal_pending() in vm_area_alloc_pages() if __GFP_NOFAIL set. This issue occurred during OPLUS KASAN TEST. Below is part of the log -&amp;gt; oom-killer sends signal to process [65731.222840] [ T1308] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/apps/uid_10198,task=gs.intelligence,pid=32454,uid=10198 [65731.259685] [T32454] Call trace: [65731.259698] [T32454]  dump_backtrace+0xf4/0x118 [65731.259734] [T32454]  show_stack+0x18/0x24 [65731.259756] [T32454]  dump_stack_lvl+0x60/0x7c [65731.259781] [T32454]  dump_stack+0x18/0x38 [65731.259800] [T32454]  mrdump_common_die+0x250/0x39c [mrdump] [65731.259936] [T32454]  ipanic_die+0x20/0x34 [mrdump] [65731.260019] [T32454]  atomic_notifier_call_chain+0xb4/0xfc [65731.260047] [T32454]  notify_die+0x114/0x198 [65731.260073] [T32454]  die+0xf4/0x5b4…&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL commit a421ef303008 (&amp;#34;mm: allow !GFP_KERNEL allocations for kvmalloc&amp;#34;) includes support for __GFP_NOFAIL, but it presents a conflict with commit dd544141b9eb (&amp;#34;vmalloc: back off when the current task is OOM-killed&amp;#34;).  A possible scenario is as follows: process-a __vmalloc_node_range(GFP_KERNEL | __GFP_NOFAIL)     __vmalloc_area_node()         vm_area_alloc_pages() 		--&amp;gt; oom-killer send SIGKILL to process-a         if (fatal_signal_pending(current)) break; --&amp;gt; return NULL; To fix this, do not check fatal_signal_pending() in vm_area_alloc_pages() if __GFP_NOFAIL set. This issue occurred during OPLUS KASAN TEST. Below is part of the log -&amp;gt; oom-killer sends signal to process [65731.222840] [ T1308] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/apps/uid_10198,task=gs.intelligence,pid=32454,uid=10198 [65731.259685] [T32454] Call trace: [65731.259698] [T32454]  dump_backtrace+0xf4/0x118 [65731.259734] [T32454]  show_stack+0x18/0x24 [65731.259756] [T32454]  dump_stack_lvl+0x60/0x7c [65731.259781] [T32454]  dump_stack+0x18/0x38 [65731.259800] [T32454]  mrdump_common_die+0x250/0x39c [mrdump] [65731.259936] [T32454]  ipanic_die+0x20/0x34 [mrdump] [65731.260019] [T32454]  atomic_notifier_call_chain+0xb4/0xfc [65731.260047] [T32454]  notify_die+0x114/0x198 [65731.260073] [T32454]  die+0xf4/0x5b4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39474</guid>
    </item>
  </channel>
</rss>
