<?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>Mon, 05 Oct 2026 14:20:43 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-04138</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04138</link>
      <description>bdu:2024-04138</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04138</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26620</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26620</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-2024-26620</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0329 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329</link>
      <description>certfr-2024-avi-0329</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329</guid>
    </item>
    <item>
      <title>EUVD-2026-345465</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345465</link>
      <description>EUVD-2026-345465</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345465</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26620</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26620</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/vfio-ap: always filter entire AP matrix&lt;/p&gt;
&lt;p&gt;The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or
domain is assigned to the mdev. The purpose of the function is to update
the guest&amp;#39;s AP configuration by filtering the matrix of adapters and
domains assigned to the mdev. When an adapter or domain is assigned, only
the APQNs associated with the APID of the new adapter or APQI of the new
domain are inspected. If an APQN does not reference a queue device bound to
the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s
matrix when updating the guest&amp;#39;s AP configuration.&lt;/p&gt;
&lt;p&gt;Inspecting only the APID of the new adapter or APQI of the new domain will
result in passing AP queues through to a guest that are not bound to the
vfio_ap device driver under certain circumstances. Consider the following:&lt;/p&gt;
&lt;p&gt;guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix):
14.0004
14.0005
14.0006
16.0004
16.0005
16.0006&lt;/p&gt;
&lt;p&gt;unassign domain 4
unbind queue 16.0005
assign domain 4&lt;/p&gt;
&lt;p&gt;When domain 4 is re-assigned, since only domain 4 will be inspected, the
APQNs that will be examined will be:
14.0004
16.0004&lt;/p&gt;
&lt;p&gt;Since both of those APQNs reference queue devices that are bound to the
vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix
when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005
will get passed through despite not being bound to the driver. This
violates…&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;s390/vfio-ap: always filter entire AP matrix&lt;/p&gt;
&lt;p&gt;The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or
domain is assigned to the mdev. The purpose of the function is to update
the guest&amp;#39;s AP configuration by filtering the matrix of adapters and
domains assigned to the mdev. When an adapter or domain is assigned, only
the APQNs associated with the APID of the new adapter or APQI of the new
domain are inspected. If an APQN does not reference a queue device bound to
the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s
matrix when updating the guest&amp;#39;s AP configuration.&lt;/p&gt;
&lt;p&gt;Inspecting only the APID of the new adapter or APQI of the new domain will
result in passing AP queues through to a guest that are not bound to the
vfio_ap device driver under certain circumstances. Consider the following:&lt;/p&gt;
&lt;p&gt;guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix):
14.0004
14.0005
14.0006
16.0004
16.0005
16.0006&lt;/p&gt;
&lt;p&gt;unassign domain 4
unbind queue 16.0005
assign domain 4&lt;/p&gt;
&lt;p&gt;When domain 4 is re-assigned, since only domain 4 will be inspected, the
APQNs that will be examined will be:
14.0004
16.0004&lt;/p&gt;
&lt;p&gt;Since both of those APQNs reference queue devices that are bound to the
vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix
when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005
will get passed through despite not being bound to the driver. This
violates…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26620</guid>
    </item>
    <item>
      <title>GHSA-43w7-7gwv-35rc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-43w7-7gwv-35rc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/vfio-ap: always filter entire AP matrix&lt;/p&gt;
&lt;p&gt;The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or
domain is assigned to the mdev. The purpose of the function is to update
the guest&amp;#39;s AP configuration by filtering the matrix of adapters and
domains assigned to the mdev. When an adapter or domain is assigned, only
the APQNs associated with the APID of the new adapter or APQI of the new
domain are inspected. If an APQN does not reference a queue device bound to
the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s
matrix when updating the guest&amp;#39;s AP configuration.&lt;/p&gt;
&lt;p&gt;Inspecting only the APID of the new adapter or APQI of the new domain will
result in passing AP queues through to a guest that are not bound to the
vfio_ap device driver under certain circumstances. Consider the following:&lt;/p&gt;
&lt;p&gt;guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix):
14.0004
14.0005
14.0006
16.0004
16.0005
16.0006&lt;/p&gt;
&lt;p&gt;unassign domain 4
unbind queue 16.0005
assign domain 4&lt;/p&gt;
&lt;p&gt;When domain 4 is re-assigned, since only domain 4 will be inspected, the
APQNs that will be examined will be:
14.0004
16.0004&lt;/p&gt;
&lt;p&gt;Since both of those APQNs reference queue devices that are bound to the
vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix
when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005
will get passed through despite not being bound to the driver. This
violates…&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;s390/vfio-ap: always filter entire AP matrix&lt;/p&gt;
&lt;p&gt;The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or
domain is assigned to the mdev. The purpose of the function is to update
the guest&amp;#39;s AP configuration by filtering the matrix of adapters and
domains assigned to the mdev. When an adapter or domain is assigned, only
the APQNs associated with the APID of the new adapter or APQI of the new
domain are inspected. If an APQN does not reference a queue device bound to
the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s
matrix when updating the guest&amp;#39;s AP configuration.&lt;/p&gt;
&lt;p&gt;Inspecting only the APID of the new adapter or APQI of the new domain will
result in passing AP queues through to a guest that are not bound to the
vfio_ap device driver under certain circumstances. Consider the following:&lt;/p&gt;
&lt;p&gt;guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix):
14.0004
14.0005
14.0006
16.0004
16.0005
16.0006&lt;/p&gt;
&lt;p&gt;unassign domain 4
unbind queue 16.0005
assign domain 4&lt;/p&gt;
&lt;p&gt;When domain 4 is re-assigned, since only domain 4 will be inspected, the
APQNs that will be examined will be:
14.0004
16.0004&lt;/p&gt;
&lt;p&gt;Since both of those APQNs reference queue devices that are bound to the
vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix
when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005
will get passed through despite not being bound to the driver. This
violates…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-43w7-7gwv-35rc</guid>
    </item>
    <item>
      <title>gsd-2024-26620</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26620</link>
      <description>gsd-2024-26620</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26620</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1466-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1466-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1466-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26620</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26620</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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: always filter entire AP matrix The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or domain is assigned to the mdev. The purpose of the function is to update the guest&amp;#39;s AP configuration by filtering the matrix of adapters and domains assigned to the mdev. When an adapter or domain is assigned, only the APQNs associated with the APID of the new adapter or APQI of the new domain are inspected. If an APQN does not reference a queue device bound to the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s matrix when updating the guest&amp;#39;s AP configuration. Inspecting only the APID of the new adapter or APQI of the new domain will result in passing AP queues through to a guest that are not bound to the vfio_ap device driver under certain circumstances. Consider the following: guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix): 14.0004 14.0005 14.0006 16.0004 16.0005 16.0006 unassign domain 4 unbind queue 16.0005 assign domain 4 When domain 4 is re-assigned, since only domain 4 will be inspected, the APQNs that will be examined will be: 14.0004 16.0004 Since both of those APQNs reference queue devices that are bound to the vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005 will get passed through despite not being bound to the driver. This violates the lin…&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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: always filter entire AP matrix The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or domain is assigned to the mdev. The purpose of the function is to update the guest&amp;#39;s AP configuration by filtering the matrix of adapters and domains assigned to the mdev. When an adapter or domain is assigned, only the APQNs associated with the APID of the new adapter or APQI of the new domain are inspected. If an APQN does not reference a queue device bound to the vfio_ap device driver, then it&amp;#39;s APID will be filtered from the mdev&amp;#39;s matrix when updating the guest&amp;#39;s AP configuration. Inspecting only the APID of the new adapter or APQI of the new domain will result in passing AP queues through to a guest that are not bound to the vfio_ap device driver under certain circumstances. Consider the following: guest&amp;#39;s AP configuration (all also assigned to the mdev&amp;#39;s matrix): 14.0004 14.0005 14.0006 16.0004 16.0005 16.0006 unassign domain 4 unbind queue 16.0005 assign domain 4 When domain 4 is re-assigned, since only domain 4 will be inspected, the APQNs that will be examined will be: 14.0004 16.0004 Since both of those APQNs reference queue devices that are bound to the vfio_ap device driver, nothing will get filtered from the mdev&amp;#39;s matrix when updating the guest&amp;#39;s AP configuration. Consequently, queue 16.0005 will get passed through despite not being bound to the driver. This violates the lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26620</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</guid>
    </item>
  </channel>
</rss>
