<?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:58:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-68802</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-68802</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-68802</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — 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-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68802</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68802</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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Limit num_syncs to prevent oversized allocations The exec and vm_bind ioctl allow userspace to specify an arbitrary num_syncs value. Without bounds checking, a very large num_syncs can force an excessively large allocation, leading to kernel warnings from the page allocator as below. Introduce DRM_XE_MAX_SYNCS (set to 1024) and reject any request exceeding this limit. &amp;#34; ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at mm/page_alloc.c:5124 __alloc_frozen_pages_noprof+0x2f8/0x2180 mm/page_alloc.c:5124 ... Call Trace:  &amp;lt;TASK&amp;gt;  alloc_pages_mpol+0xe4/0x330 mm/mempolicy.c:2416  ___kmalloc_large_node+0xd8/0x110 mm/slub.c:4317  __kmalloc_large_node_noprof+0x18/0xe0 mm/slub.c:4348  __do_kmalloc_node mm/slub.c:4364 [inline]  __kmalloc_noprof+0x3d4/0x4b0 mm/slub.c:4388  kmalloc_noprof include/linux/slab.h:909 [inline]  kmalloc_array_noprof include/linux/slab.h:948 [inline]  xe_exec_ioctl+0xa47/0x1e70 drivers/gpu/drm/xe/xe_exec.c:158  drm_ioctl_kernel+0x1f1/0x3e0 drivers/gpu/drm/drm_ioctl.c:797  drm_ioctl+0x5e7/0xc50 drivers/gpu/drm/drm_ioctl.c:894  xe_drm_ioctl+0x10b/0x170 drivers/gpu/drm/xe/xe_device.c:224  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:598 [inline]  __se_sys_ioctl fs/ioctl.c:584 [inline]  __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0xbb/0x380 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_aft…&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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Limit num_syncs to prevent oversized allocations The exec and vm_bind ioctl allow userspace to specify an arbitrary num_syncs value. Without bounds checking, a very large num_syncs can force an excessively large allocation, leading to kernel warnings from the page allocator as below. Introduce DRM_XE_MAX_SYNCS (set to 1024) and reject any request exceeding this limit. &amp;#34; ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at mm/page_alloc.c:5124 __alloc_frozen_pages_noprof+0x2f8/0x2180 mm/page_alloc.c:5124 ... Call Trace:  &amp;lt;TASK&amp;gt;  alloc_pages_mpol+0xe4/0x330 mm/mempolicy.c:2416  ___kmalloc_large_node+0xd8/0x110 mm/slub.c:4317  __kmalloc_large_node_noprof+0x18/0xe0 mm/slub.c:4348  __do_kmalloc_node mm/slub.c:4364 [inline]  __kmalloc_noprof+0x3d4/0x4b0 mm/slub.c:4388  kmalloc_noprof include/linux/slab.h:909 [inline]  kmalloc_array_noprof include/linux/slab.h:948 [inline]  xe_exec_ioctl+0xa47/0x1e70 drivers/gpu/drm/xe/xe_exec.c:158  drm_ioctl_kernel+0x1f1/0x3e0 drivers/gpu/drm/drm_ioctl.c:797  drm_ioctl+0x5e7/0xc50 drivers/gpu/drm/drm_ioctl.c:894  xe_drm_ioctl+0x10b/0x170 drivers/gpu/drm/xe/xe_device.c:224  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:598 [inline]  __se_sys_ioctl fs/ioctl.c:584 [inline]  __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0xbb/0x380 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_aft…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68802</guid>
    </item>
  </channel>
</rss>
