<?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 02:36:50 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:19930 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2025:19930</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)
  * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)
  * kernel: x86/vmscape: Add conditional IBPB mitigation (CVE-2025-40300)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)
  * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)
  * kernel: x86/vmscape: Add conditional IBPB mitigation (CVE-2025-40300)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2025:19930</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-40300</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-40300</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-40300</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-2026-1337 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-1337</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;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&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;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-1337</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40300</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40300</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already protect kernel/KVM from a malicious guest. Userspace can additionally be protected by flushing the branch predictors after a VMexit. Since it is the userspace that consumes the poisoned branch predictors, conditionally issue an IBPB after a VMexit and before returning to userspace. Workloads that frequently switch between hypervisor and userspace will incur the most overhead from the new IBPB. This new IBPB is not integrated with the existing IBPB sites. For instance, a task can use the existing speculation control prctl() to get an IBPB at context switch time. With this implementation, the IBPB is doubled up: one at context switch and another before running userspace. The intent is to integrate and optimize these cases post-embargo. [ dhansen: elaborate on suboptimal IBPB solution ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already protect kernel/KVM from a malicious guest. Userspace can additionally be protected by flushing the branch predictors after a VMexit. Since it is the userspace that consumes the poisoned branch predictors, conditionally issue an IBPB after a VMexit and before returning to userspace. Workloads that frequently switch between hypervisor and userspace will incur the most overhead from the new IBPB. This new IBPB is not integrated with the existing IBPB sites. For instance, a task can use the existing speculation control prctl() to get an IBPB at context switch time. With this implementation, the IBPB is doubled up: one at context switch and another before running userspace. The intent is to integrate and optimize these cases post-embargo. [ dhansen: elaborate on suboptimal IBPB solution ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40300</guid>
    </item>
  </channel>
</rss>
