<?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://vulnerability.circl.lu</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, 28 Sep 2026 10:46:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89958</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-89958</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://vulnerability.circl.lu/vuln/bell-cve-2026-89958</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89958</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89958</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/vfio-ap: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL&lt;/p&gt;
&lt;p&gt;The ap_driver structure has two fields which are function pointers to
callbacks:&lt;/p&gt;
&lt;p&gt;* .on_config_changed: called at the start of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the associated AP
                      devices will be added or removed accordingly. This
                      gives the implementor a chance to evaluate the
                      configuration changes and respond to them before
                      the associated devices are added or removed.&lt;/p&gt;
&lt;p&gt;* .on_scan_complete:  Called at the end of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the AP devices have
                      been added or removed accordingly. This gives the
                      implementor the opportunity to respond to the
                      changes after the associated devices are added or
                      removed.&lt;/p&gt;
&lt;p&gt;These two callbacks are implemented in the vfio_ap device driver via the
vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively.&lt;/p&gt;
&lt;p&gt;Within the call stack of these two callback functions the
matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether
matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never b…&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: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL&lt;/p&gt;
&lt;p&gt;The ap_driver structure has two fields which are function pointers to
callbacks:&lt;/p&gt;
&lt;p&gt;* .on_config_changed: called at the start of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the associated AP
                      devices will be added or removed accordingly. This
                      gives the implementor a chance to evaluate the
                      configuration changes and respond to them before
                      the associated devices are added or removed.&lt;/p&gt;
&lt;p&gt;* .on_scan_complete:  Called at the end of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the AP devices have
                      been added or removed accordingly. This gives the
                      implementor the opportunity to respond to the
                      changes after the associated devices are added or
                      removed.&lt;/p&gt;
&lt;p&gt;These two callbacks are implemented in the vfio_ap device driver via the
vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively.&lt;/p&gt;
&lt;p&gt;Within the call stack of these two callback functions the
matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether
matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-89958</guid>
    </item>
    <item>
      <title>GHSA-hgjh-2rgq-2xcv</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hgjh-2rgq-2xcv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/vfio-ap: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL&lt;/p&gt;
&lt;p&gt;The ap_driver structure has two fields which are function pointers to
callbacks:&lt;/p&gt;
&lt;p&gt;* .on_config_changed: called at the start of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the associated AP
                      devices will be added or removed accordingly. This
                      gives the implementor a chance to evaluate the
                      configuration changes and respond to them before
                      the associated devices are added or removed.&lt;/p&gt;
&lt;p&gt;* .on_scan_complete:  Called at the end of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the AP devices have
                      been added or removed accordingly. This gives the
                      implementor the opportunity to respond to the
                      changes after the associated devices are added or
                      removed.&lt;/p&gt;
&lt;p&gt;These two callbacks are implemented in the vfio_ap device driver via the
vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively.&lt;/p&gt;
&lt;p&gt;Within the call stack of these two callback functions the
matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether
matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never b…&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: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL&lt;/p&gt;
&lt;p&gt;The ap_driver structure has two fields which are function pointers to
callbacks:&lt;/p&gt;
&lt;p&gt;* .on_config_changed: called at the start of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the associated AP
                      devices will be added or removed accordingly. This
                      gives the implementor a chance to evaluate the
                      configuration changes and respond to them before
                      the associated devices are added or removed.&lt;/p&gt;
&lt;p&gt;* .on_scan_complete:  Called at the end of the AP bus scan function to
                      notify the device driver that the host AP
                      configuration has changed and the AP devices have
                      been added or removed accordingly. This gives the
                      implementor the opportunity to respond to the
                      changes after the associated devices are added or
                      removed.&lt;/p&gt;
&lt;p&gt;These two callbacks are implemented in the vfio_ap device driver via the
vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively.&lt;/p&gt;
&lt;p&gt;Within the call stack of these two callback functions the
matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether
matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hgjh-2rgq-2xcv</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89958</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89958</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL The ap_driver structure has two fields which are function pointers to callbacks: * .on_config_changed: called at the start of the AP bus scan function to                       notify the device driver that the host AP                       configuration has changed and the associated AP                       devices will be added or removed accordingly. This                       gives the implementor a chance to evaluate the                       configuration changes and respond to them before                       the associated devices are added or removed. * .on_scan_complete:  Called at the end of the AP bus scan function to                       notify the device driver that the host AP                       configuration has changed and the AP devices have                       been added or removed accordingly. This gives the                       implementor the opportunity to respond to the                       changes after the associated devices are added or                       removed. These two callbacks are implemented in the vfio_ap device driver via the vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively. Within the call stack of these two callback functions the matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never been se…&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix dereference matrix_mdev-&amp;gt;kvm without checking for NULL The ap_driver structure has two fields which are function pointers to callbacks: * .on_config_changed: called at the start of the AP bus scan function to                       notify the device driver that the host AP                       configuration has changed and the associated AP                       devices will be added or removed accordingly. This                       gives the implementor a chance to evaluate the                       configuration changes and respond to them before                       the associated devices are added or removed. * .on_scan_complete:  Called at the end of the AP bus scan function to                       notify the device driver that the host AP                       configuration has changed and the AP devices have                       been added or removed accordingly. This gives the                       implementor the opportunity to respond to the                       changes after the associated devices are added or                       removed. These two callbacks are implemented in the vfio_ap device driver via the vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively. Within the call stack of these two callback functions the matrix_mdev-&amp;gt;kvm-&amp;gt;lock mutex is taken without checking whether matrix_mdev-&amp;gt;kvm is NULL or not. If matrix_mdev-&amp;gt;kvm has never been se…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89958</guid>
    </item>
  </channel>
</rss>
