<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 07:31:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98716</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98716</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://cve.radiocsirt.org/vuln/bell-cve-2026-98716</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>EUVD-2026-396024</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396024</link>
      <description>EUVD-2026-396024</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396024</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98716</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98716</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted&lt;/p&gt;
&lt;p&gt;Use the MSR permission bitmap of the active VMCB instead of assuming that
KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02
if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM
needs to merge msprm01 with msrpm12.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used,
as __va() is cheap on x86, and caching the virtual address would introduce
yet another source of potentially stale information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted&lt;/p&gt;
&lt;p&gt;Use the MSR permission bitmap of the active VMCB instead of assuming that
KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02
if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM
needs to merge msprm01 with msrpm12.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used,
as __va() is cheap on x86, and caching the virtual address would introduce
yet another source of potentially stale information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98716</guid>
    </item>
    <item>
      <title>GHSA-hpgm-5w85-35mm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hpgm-5w85-35mm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted&lt;/p&gt;
&lt;p&gt;Use the MSR permission bitmap of the active VMCB instead of assuming that
KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02
if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM
needs to merge msprm01 with msrpm12.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used,
as __va() is cheap on x86, and caching the virtual address would introduce
yet another source of potentially stale information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted&lt;/p&gt;
&lt;p&gt;Use the MSR permission bitmap of the active VMCB instead of assuming that
KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02
if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM
needs to merge msprm01 with msrpm12.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used,
as __va() is cheap on x86, and caching the virtual address would introduce
yet another source of potentially stale information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hpgm-5w85-35mm</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98716 — KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98716</link>
      <description>msrc_CVE-2026-98716</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98716</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98716</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98716</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-kvm, Ubuntu:Pro:FIPS-updates:16.04:LTS: linux-fips, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-kvm, Ubuntu:Pro:FIPS-updates:16.04:LTS: linux-fips, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB&amp;#39;s MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&amp;#39;s bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don&amp;#39;t bother tracking the virtual address of the bitmap that&amp;#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98716</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
