<?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:17:48 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37761</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37761</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-37761</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0559 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0559</link>
      <description>certfr-2025-avi-0559</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0559</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37761</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37761</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 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix an out-of-bounds shift when invalidating TLB When the size of the range invalidated is larger than rounddown_pow_of_two(ULONG_MAX), The function macro roundup_pow_of_two(length) will hit an out-of-bounds shift [1]. Use a full TLB invalidation for such cases. v2: - Use a define for the range size limit over which we use a full   TLB invalidation. (Lucas) - Use a better calculation of the limit. [1]: [   39.202421] ------------[ cut here ]------------ [   39.202657] UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13 [   39.202673] shift exponent 64 is too large for 64-bit type &amp;#39;long unsigned int&amp;#39; [   39.202688] CPU: 8 UID: 0 PID: 3129 Comm: xe_exec_system_ Tainted: G U             6.14.0+ #10 [   39.202690] Tainted: [U]=USER [   39.202690] Hardware name: ASUS System Product Name/PRIME B560M-A AC, BIOS 2001 02/01/2023 [   39.202691] Call Trace: [   39.202692]  &amp;lt;TASK&amp;gt; [   39.202695]  dump_stack_lvl+0x6e/0xa0 [   39.202699]  ubsan_epilogue+0x5/0x30 [   39.202701]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe6 [   39.202705]  xe_gt_tlb_invalidation_range.cold+0x1d/0x3a [xe] [   39.202800]  ? find_held_lock+0x2b/0x80 [   39.202803]  ? mark_held_locks+0x40/0x70 [   39.202806]  xe_svm_invalidate+0x459/0x700 [xe] [   39.202897]  drm_gpusvm_notifier_invalidate+0x4d/0x70 [drm_gpusvm] [   39.202900]  __mmu_notifier_release+0x1f5/0x270 [   39.202905]  exit_mmap+0x40e/0x450 [   39.202912]  __mmput+0…&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 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix an out-of-bounds shift when invalidating TLB When the size of the range invalidated is larger than rounddown_pow_of_two(ULONG_MAX), The function macro roundup_pow_of_two(length) will hit an out-of-bounds shift [1]. Use a full TLB invalidation for such cases. v2: - Use a define for the range size limit over which we use a full   TLB invalidation. (Lucas) - Use a better calculation of the limit. [1]: [   39.202421] ------------[ cut here ]------------ [   39.202657] UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13 [   39.202673] shift exponent 64 is too large for 64-bit type &amp;#39;long unsigned int&amp;#39; [   39.202688] CPU: 8 UID: 0 PID: 3129 Comm: xe_exec_system_ Tainted: G U             6.14.0+ #10 [   39.202690] Tainted: [U]=USER [   39.202690] Hardware name: ASUS System Product Name/PRIME B560M-A AC, BIOS 2001 02/01/2023 [   39.202691] Call Trace: [   39.202692]  &amp;lt;TASK&amp;gt; [   39.202695]  dump_stack_lvl+0x6e/0xa0 [   39.202699]  ubsan_epilogue+0x5/0x30 [   39.202701]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe6 [   39.202705]  xe_gt_tlb_invalidation_range.cold+0x1d/0x3a [xe] [   39.202800]  ? find_held_lock+0x2b/0x80 [   39.202803]  ? mark_held_locks+0x40/0x70 [   39.202806]  xe_svm_invalidate+0x459/0x700 [xe] [   39.202897]  drm_gpusvm_notifier_invalidate+0x4d/0x70 [drm_gpusvm] [   39.202900]  __mmu_notifier_release+0x1f5/0x270 [   39.202905]  exit_mmap+0x40e/0x450 [   39.202912]  __mmput+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37761</guid>
    </item>
  </channel>
</rss>
