<?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 03:42:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31573 — media: verisilicon: Fix kernel panic due to __initconst misuse</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31573</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;media: verisilicon: Fix kernel panic due to __initconst misuse&lt;/p&gt;
&lt;p&gt;Fix a kernel panic when probing the driver as a module:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address
  ffffd9c18eb05000
  of_find_matching_node_and_match+0x5c/0x1a0
  hantro_probe+0x2f4/0x7d0 [hantro_vpu]&lt;/p&gt;
&lt;p&gt;The imx8mq_vpu_shared_resources array is referenced by variant
structures through their shared_devices field. When built as a
module, __initconst causes this data to be freed after module
init, but it&amp;#39;s later accessed during probe, causing a page fault.&lt;/p&gt;
&lt;p&gt;The imx8mq_vpu_shared_resources is referenced from non-init code,
so keeping __initconst or __initconst_or_module here is wrong.&lt;/p&gt;
&lt;p&gt;Drop the __initconst annotation and let it live in the normal .rodata
section.&lt;/p&gt;
&lt;p&gt;A bug of __initconst called from regular non-init probe code
leading to bugs during probe deferrals or during unbind-bind cycles.&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;media: verisilicon: Fix kernel panic due to __initconst misuse&lt;/p&gt;
&lt;p&gt;Fix a kernel panic when probing the driver as a module:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address
  ffffd9c18eb05000
  of_find_matching_node_and_match+0x5c/0x1a0
  hantro_probe+0x2f4/0x7d0 [hantro_vpu]&lt;/p&gt;
&lt;p&gt;The imx8mq_vpu_shared_resources array is referenced by variant
structures through their shared_devices field. When built as a
module, __initconst causes this data to be freed after module
init, but it&amp;#39;s later accessed during probe, causing a page fault.&lt;/p&gt;
&lt;p&gt;The imx8mq_vpu_shared_resources is referenced from non-init code,
so keeping __initconst or __initconst_or_module here is wrong.&lt;/p&gt;
&lt;p&gt;Drop the __initconst annotation and let it live in the normal .rodata
section.&lt;/p&gt;
&lt;p&gt;A bug of __initconst called from regular non-init probe code
leading to bugs during probe deferrals or during unbind-bind cycles.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31573</guid>
    </item>
  </channel>
</rss>
