https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 22:06:41 +0000 https://vulnerability.circl.lu/vuln/cve-2026-93251 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ACPI: bus: Introduce acpi_bus_get_primary_device()</p> <p>The function used for obtaining the first &#34;physical&#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&#39;s physical_node_lock in acpi_get_first_physical_node() and before it returns. The last reference to the &#34;physical&#34; device may be dropped then before the pointer to it is returned to the caller.</p> <p>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.</p> <p>To prepare for addressing this problem, introduce a new function for getting the first &#34;physical&#34; device associated with the given ACPI one (the &#34;primary physical device&#34;) that will also reference count the device in question before returning a pointer to it.</p> <p>Make that new function and acpi_get_first_physical_node() share the physical node list lookup code.</p> <p>No intentional functional impact.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ACPI: bus: Introduce acpi_bus_get_primary_device()</p> <p>The function used for obtaining the first &#34;physical&#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&#39;s physical_node_lock in acpi_get_first_physical_node() and before it returns. The last reference to the &#34;physical&#34; device may be dropped then before the pointer to it is returned to the caller.</p> <p>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.</p> <p>To prepare for addressing this problem, introduce a new function for getting the first &#34;physical&#34; device associated with the given ACPI one (the &#34;primary physical device&#34;) that will also reference count the device in question before returning a pointer to it.</p> <p>Make that new function and acpi_get_first_physical_node() share the physical node list lookup code.</p> <p>No intentional functional impact.</p> https://vulnerability.circl.lu/vuln/cve-2026-93251