<?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 09:29:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93114</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93114</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-93114</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93114</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93114</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/surface: acpi-notify: Check ACPI companion before use&lt;/p&gt;
&lt;p&gt;Since every platform driver can be forced to match a device that doesn&amp;#39;t
match its list of device IDs because of device_match_driver_override(),
platform drivers that rely on the existence of a device&amp;#39;s ACPI companion
object should verify its presence.&lt;/p&gt;
&lt;p&gt;san_probe() dereferences the result of ACPI_COMPANION() when installing
the GSBUS address space handler, so force-binding the driver to a device
without an ACPI companion leads to a NULL pointer dereference.  The
dereference was introduced when the probe function was switched from
ACPI_HANDLE() to ACPI_COMPANION().&lt;/p&gt;
&lt;p&gt;Check the ACPI companion against NULL and return -ENODEV when it is
missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION()
against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&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;platform/surface: acpi-notify: Check ACPI companion before use&lt;/p&gt;
&lt;p&gt;Since every platform driver can be forced to match a device that doesn&amp;#39;t
match its list of device IDs because of device_match_driver_override(),
platform drivers that rely on the existence of a device&amp;#39;s ACPI companion
object should verify its presence.&lt;/p&gt;
&lt;p&gt;san_probe() dereferences the result of ACPI_COMPANION() when installing
the GSBUS address space handler, so force-binding the driver to a device
without an ACPI companion leads to a NULL pointer dereference.  The
dereference was introduced when the probe function was switched from
ACPI_HANDLE() to ACPI_COMPANION().&lt;/p&gt;
&lt;p&gt;Check the ACPI companion against NULL and return -ENODEV when it is
missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION()
against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-93114</guid>
    </item>
    <item>
      <title>GHSA-fmfr-wc4p-75cj</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-fmfr-wc4p-75cj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/surface: acpi-notify: Check ACPI companion before use&lt;/p&gt;
&lt;p&gt;Since every platform driver can be forced to match a device that doesn&amp;#39;t
match its list of device IDs because of device_match_driver_override(),
platform drivers that rely on the existence of a device&amp;#39;s ACPI companion
object should verify its presence.&lt;/p&gt;
&lt;p&gt;san_probe() dereferences the result of ACPI_COMPANION() when installing
the GSBUS address space handler, so force-binding the driver to a device
without an ACPI companion leads to a NULL pointer dereference.  The
dereference was introduced when the probe function was switched from
ACPI_HANDLE() to ACPI_COMPANION().&lt;/p&gt;
&lt;p&gt;Check the ACPI companion against NULL and return -ENODEV when it is
missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION()
against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&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;platform/surface: acpi-notify: Check ACPI companion before use&lt;/p&gt;
&lt;p&gt;Since every platform driver can be forced to match a device that doesn&amp;#39;t
match its list of device IDs because of device_match_driver_override(),
platform drivers that rely on the existence of a device&amp;#39;s ACPI companion
object should verify its presence.&lt;/p&gt;
&lt;p&gt;san_probe() dereferences the result of ACPI_COMPANION() when installing
the GSBUS address space handler, so force-binding the driver to a device
without an ACPI companion leads to a NULL pointer dereference.  The
dereference was introduced when the probe function was switched from
ACPI_HANDLE() to ACPI_COMPANION().&lt;/p&gt;
&lt;p&gt;Check the ACPI companion against NULL and return -ENODEV when it is
missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION()
against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-fmfr-wc4p-75cj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-93114 — platform/surface: acpi-notify: Check ACPI companion before use</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-93114</link>
      <description>msrc_CVE-2026-93114</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-93114</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-93114</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93114</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/surface: acpi-notify: Check ACPI companion before use Since every platform driver can be forced to match a device that doesn&amp;#39;t match its list of device IDs because of device_match_driver_override(), platform drivers that rely on the existence of a device&amp;#39;s ACPI companion object should verify its presence. san_probe() dereferences the result of ACPI_COMPANION() when installing the GSBUS address space handler, so force-binding the driver to a device without an ACPI companion leads to a NULL pointer dereference.  The dereference was introduced when the probe function was switched from ACPI_HANDLE() to ACPI_COMPANION(). Check the ACPI companion against NULL and return -ENODEV when it is missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION() against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/surface: acpi-notify: Check ACPI companion before use Since every platform driver can be forced to match a device that doesn&amp;#39;t match its list of device IDs because of device_match_driver_override(), platform drivers that rely on the existence of a device&amp;#39;s ACPI companion object should verify its presence. san_probe() dereferences the result of ACPI_COMPANION() when installing the GSBUS address space handler, so force-binding the driver to a device without an ACPI companion leads to a NULL pointer dereference.  The dereference was introduced when the probe function was switched from ACPI_HANDLE() to ACPI_COMPANION(). Check the ACPI companion against NULL and return -ENODEV when it is missing, like commit e4865a56d013 (&amp;#34;ACPI: driver: Check ACPI_COMPANION() against NULL during probe&amp;#34;) does for the core ACPI platform drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93114</guid>
    </item>
  </channel>
</rss>
