<?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>Tue, 29 Sep 2026 04:43:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71118 — ACPICA: Avoid walking the Namespace if start_node is NULL</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71118</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPICA: Avoid walking the Namespace if start_node is NULL&lt;/p&gt;
&lt;p&gt;Although commit 0c9992315e73 (&amp;#34;ACPICA: Avoid walking the ACPI Namespace
if it is not there&amp;#34;) fixed the situation when both start_node and
acpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed
on Honor Magicbook 14 Pro [1].&lt;/p&gt;
&lt;p&gt;That happens due to the access to the member of parent_node in
acpi_ns_get_next_node().  The NULL pointer dereference will always
happen, no matter whether or not the start_node is equal to
ACPI_ROOT_OBJECT, so move the check of start_node being NULL
out of the if block.&lt;/p&gt;
&lt;p&gt;Unfortunately, all the attempts to contact Honor have failed, they
refused to provide any technical support for Linux.&lt;/p&gt;
&lt;p&gt;The bad DSDT table&amp;#39;s dump could be found on GitHub [2].&lt;/p&gt;
&lt;p&gt;DMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025&lt;/p&gt;
&lt;p&gt;[ rjw: Subject adjustment, changelog edits ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPICA: Avoid walking the Namespace if start_node is NULL&lt;/p&gt;
&lt;p&gt;Although commit 0c9992315e73 (&amp;#34;ACPICA: Avoid walking the ACPI Namespace
if it is not there&amp;#34;) fixed the situation when both start_node and
acpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed
on Honor Magicbook 14 Pro [1].&lt;/p&gt;
&lt;p&gt;That happens due to the access to the member of parent_node in
acpi_ns_get_next_node().  The NULL pointer dereference will always
happen, no matter whether or not the start_node is equal to
ACPI_ROOT_OBJECT, so move the check of start_node being NULL
out of the if block.&lt;/p&gt;
&lt;p&gt;Unfortunately, all the attempts to contact Honor have failed, they
refused to provide any technical support for Linux.&lt;/p&gt;
&lt;p&gt;The bad DSDT table&amp;#39;s dump could be found on GitHub [2].&lt;/p&gt;
&lt;p&gt;DMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025&lt;/p&gt;
&lt;p&gt;[ rjw: Subject adjustment, changelog edits ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71118</guid>
    </item>
  </channel>
</rss>
