<?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 15:32:10 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93251</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93251</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-93251</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93251</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93251</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPI: bus: Introduce acpi_bus_get_primary_device()&lt;/p&gt;
&lt;p&gt;The function used for obtaining the first &amp;#34;physical&amp;#34; device for which
the given ACPI one is the ACPI companion, acpi_get_first_physical_node(),
may return a stale device pointer (mostly in theory) because
acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s
physical_node_lock in acpi_get_first_physical_node() and before it
returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped
then before the pointer to it is returned to the caller.&lt;/p&gt;
&lt;p&gt;If that happens and the acpi_get_first_physical_node() caller invokes
get_device() on the pointer obtained from it, which is done by the
majority of its callers, a use-after-free will occur.&lt;/p&gt;
&lt;p&gt;To prepare for addressing this problem, introduce a new function for
getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one
(the &amp;#34;primary physical device&amp;#34;) that will also reference count the
device in question before returning a pointer to it.&lt;/p&gt;
&lt;p&gt;Make that new function and acpi_get_first_physical_node() share the
physical node list lookup code.&lt;/p&gt;
&lt;p&gt;No intentional functional impact.&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;ACPI: bus: Introduce acpi_bus_get_primary_device()&lt;/p&gt;
&lt;p&gt;The function used for obtaining the first &amp;#34;physical&amp;#34; device for which
the given ACPI one is the ACPI companion, acpi_get_first_physical_node(),
may return a stale device pointer (mostly in theory) because
acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s
physical_node_lock in acpi_get_first_physical_node() and before it
returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped
then before the pointer to it is returned to the caller.&lt;/p&gt;
&lt;p&gt;If that happens and the acpi_get_first_physical_node() caller invokes
get_device() on the pointer obtained from it, which is done by the
majority of its callers, a use-after-free will occur.&lt;/p&gt;
&lt;p&gt;To prepare for addressing this problem, introduce a new function for
getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one
(the &amp;#34;primary physical device&amp;#34;) that will also reference count the
device in question before returning a pointer to it.&lt;/p&gt;
&lt;p&gt;Make that new function and acpi_get_first_physical_node() share the
physical node list lookup code.&lt;/p&gt;
&lt;p&gt;No intentional functional impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-93251</guid>
    </item>
    <item>
      <title>GHSA-2qvg-p8g6-fm8w</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2qvg-p8g6-fm8w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPI: bus: Introduce acpi_bus_get_primary_device()&lt;/p&gt;
&lt;p&gt;The function used for obtaining the first &amp;#34;physical&amp;#34; device for which
the given ACPI one is the ACPI companion, acpi_get_first_physical_node(),
may return a stale device pointer (mostly in theory) because
acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s
physical_node_lock in acpi_get_first_physical_node() and before it
returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped
then before the pointer to it is returned to the caller.&lt;/p&gt;
&lt;p&gt;If that happens and the acpi_get_first_physical_node() caller invokes
get_device() on the pointer obtained from it, which is done by the
majority of its callers, a use-after-free will occur.&lt;/p&gt;
&lt;p&gt;To prepare for addressing this problem, introduce a new function for
getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one
(the &amp;#34;primary physical device&amp;#34;) that will also reference count the
device in question before returning a pointer to it.&lt;/p&gt;
&lt;p&gt;Make that new function and acpi_get_first_physical_node() share the
physical node list lookup code.&lt;/p&gt;
&lt;p&gt;No intentional functional impact.&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;ACPI: bus: Introduce acpi_bus_get_primary_device()&lt;/p&gt;
&lt;p&gt;The function used for obtaining the first &amp;#34;physical&amp;#34; device for which
the given ACPI one is the ACPI companion, acpi_get_first_physical_node(),
may return a stale device pointer (mostly in theory) because
acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s
physical_node_lock in acpi_get_first_physical_node() and before it
returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped
then before the pointer to it is returned to the caller.&lt;/p&gt;
&lt;p&gt;If that happens and the acpi_get_first_physical_node() caller invokes
get_device() on the pointer obtained from it, which is done by the
majority of its callers, a use-after-free will occur.&lt;/p&gt;
&lt;p&gt;To prepare for addressing this problem, introduce a new function for
getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one
(the &amp;#34;primary physical device&amp;#34;) that will also reference count the
device in question before returning a pointer to it.&lt;/p&gt;
&lt;p&gt;Make that new function and acpi_get_first_physical_node() share the
physical node list lookup code.&lt;/p&gt;
&lt;p&gt;No intentional functional impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2qvg-p8g6-fm8w</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93251</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93251</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ACPI: bus: Introduce acpi_bus_get_primary_device() The function used for obtaining the first &amp;#34;physical&amp;#34; device for which the given ACPI one is the ACPI companion, acpi_get_first_physical_node(), may return a stale device pointer (mostly in theory) because acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s physical_node_lock in acpi_get_first_physical_node() and before it returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped then before the pointer to it is returned to the caller. If that happens and the acpi_get_first_physical_node() caller invokes get_device() on the pointer obtained from it, which is done by the majority of its callers, a use-after-free will occur. To prepare for addressing this problem, introduce a new function for getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one (the &amp;#34;primary physical device&amp;#34;) that will also reference count the device in question before returning a pointer to it. Make that new function and acpi_get_first_physical_node() share the physical node list lookup code. No intentional functional impact.&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ACPI: bus: Introduce acpi_bus_get_primary_device() The function used for obtaining the first &amp;#34;physical&amp;#34; device for which the given ACPI one is the ACPI companion, acpi_get_first_physical_node(), may return a stale device pointer (mostly in theory) because acpi_unbind_one() may run as a whole after dropping the ACPI device&amp;#39;s physical_node_lock in acpi_get_first_physical_node() and before it returns.  The last reference to the &amp;#34;physical&amp;#34; device may be dropped then before the pointer to it is returned to the caller. If that happens and the acpi_get_first_physical_node() caller invokes get_device() on the pointer obtained from it, which is done by the majority of its callers, a use-after-free will occur. To prepare for addressing this problem, introduce a new function for getting the first &amp;#34;physical&amp;#34; device associated with the given ACPI one (the &amp;#34;primary physical device&amp;#34;) that will also reference count the device in question before returning a pointer to it. Make that new function and acpi_get_first_physical_node() share the physical node list lookup code. No intentional functional impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93251</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder 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 herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
