<?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 10:55:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21662</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21662</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-21662</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>OESA-2025-1318 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1318</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU&lt;/p&gt;
&lt;p&gt;Zap both valid and invalid roots when zapping/unmapping a gfn range, as
KVM must ensure it holds no references to the freed page after returning
from the unmap operation.  Most notably, the TDP MMU doesn&amp;amp;apos;t zap invalid
roots in mmu_notifier callbacks.  This leads to use-after-free and other
issues if the mmu_notifier runs to completion while an invalid root
zapper yields as KVM fails to honor the requirement that there must be
_no_ references to the page after the mmu_notifier returns.&lt;/p&gt;
&lt;p&gt;The bug is most easily reproduced by hacking KVM to cause a collision
between set_nx_huge_pages() and kvm_mmu_notifier_release(), but the bug
exists between kvm_mmu_notifier_invalidate_range_start() and memslot
updates as well.  Invalidating a root ensures pages aren&amp;amp;apos;t accessible by
the guest, and KVM won&amp;amp;apos;t read or write page data itself, but KVM will
trigger e.g. kvm_set_pfn_dirty() when zapping SPTEs, and thus completing
a zap of an invalid root _after_ the mmu_notifier returns is fatal.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 24 PID: 1496 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:173 [kvm]
  RIP: 0010:kvm_is_zone_device_pfn+0x96/0xa0 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   kvm_set_pfn_dirty+0xa8/0xe0 [kvm]
   __handle_changed_spte+0x2ab/0x5e0 [kvm]
   __handle_changed_spte+0x2ab/0x5e0 [kvm]…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU&lt;/p&gt;
&lt;p&gt;Zap both valid and invalid roots when zapping/unmapping a gfn range, as
KVM must ensure it holds no references to the freed page after returning
from the unmap operation.  Most notably, the TDP MMU doesn&amp;amp;apos;t zap invalid
roots in mmu_notifier callbacks.  This leads to use-after-free and other
issues if the mmu_notifier runs to completion while an invalid root
zapper yields as KVM fails to honor the requirement that there must be
_no_ references to the page after the mmu_notifier returns.&lt;/p&gt;
&lt;p&gt;The bug is most easily reproduced by hacking KVM to cause a collision
between set_nx_huge_pages() and kvm_mmu_notifier_release(), but the bug
exists between kvm_mmu_notifier_invalidate_range_start() and memslot
updates as well.  Invalidating a root ensures pages aren&amp;amp;apos;t accessible by
the guest, and KVM won&amp;amp;apos;t read or write page data itself, but KVM will
trigger e.g. kvm_set_pfn_dirty() when zapping SPTEs, and thus completing
a zap of an invalid root _after_ the mmu_notifier returns is fatal.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 24 PID: 1496 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:173 [kvm]
  RIP: 0010:kvm_is_zone_device_pfn+0x96/0xa0 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   kvm_set_pfn_dirty+0xa8/0xe0 [kvm]
   __handle_changed_spte+0x2ab/0x5e0 [kvm]
   __handle_changed_spte+0x2ab/0x5e0 [kvm]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1318</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21662</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21662</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix variable not being completed when function returns When cmd_alloc_index(), fails cmd_work_handler() needs to complete ent-&amp;gt;slotted before returning early. Otherwise the task which issued the command may hang:    mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry    INFO: task kworker/13:2:4055883 blocked for more than 120 seconds.          Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1    &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.    kworker/13:2    D    0 4055883      2 0x00000228    Workqueue: events mlx5e_tx_dim_work [mlx5_core]    Call trace:       __switch_to+0xe8/0x150       __schedule+0x2a8/0x9b8       schedule+0x2c/0x88       schedule_timeout+0x204/0x478       wait_for_common+0x154/0x250       wait_for_completion+0x28/0x38       cmd_exec+0x7a0/0xa00 [mlx5_core]       mlx5_cmd_exec+0x54/0x80 [mlx5_core]       mlx5_core_modify_cq+0x6c/0x80 [mlx5_core]       mlx5_core_modify_cq_moderation+0xa0/0xb8 [mlx5_core]       mlx5e_tx_dim_work+0x54/0x68 [mlx5_core]       process_one_work+0x1b0/0x448       worker_thread+0x54/0x468       kthread+0x134/0x138       ret_from_fork+0x10/0x18&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix variable not being completed when function returns When cmd_alloc_index(), fails cmd_work_handler() needs to complete ent-&amp;gt;slotted before returning early. Otherwise the task which issued the command may hang:    mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry    INFO: task kworker/13:2:4055883 blocked for more than 120 seconds.          Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1    &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.    kworker/13:2    D    0 4055883      2 0x00000228    Workqueue: events mlx5e_tx_dim_work [mlx5_core]    Call trace:       __switch_to+0xe8/0x150       __schedule+0x2a8/0x9b8       schedule+0x2c/0x88       schedule_timeout+0x204/0x478       wait_for_common+0x154/0x250       wait_for_completion+0x28/0x38       cmd_exec+0x7a0/0xa00 [mlx5_core]       mlx5_cmd_exec+0x54/0x80 [mlx5_core]       mlx5_core_modify_cq+0x6c/0x80 [mlx5_core]       mlx5_core_modify_cq_moderation+0xa0/0xb8 [mlx5_core]       mlx5e_tx_dim_work+0x54/0x68 [mlx5_core]       process_one_work+0x1b0/0x448       worker_thread+0x54/0x468       kthread+0x134/0x138       ret_from_fork+0x10/0x18&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21662</guid>
    </item>
  </channel>
</rss>
