<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T19:31:17.591473+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-31573</id>
    <title>CVE-2026-31573 — media: verisilicon: Fix kernel panic due to __initconst misuse</title>
    <updated>2026-09-29T19:31:17.691010+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>media: verisilicon: Fix kernel panic due to __initconst misuse</p>
<p>Fix a kernel panic when probing the driver as a module:</p>
<p>Unable to handle kernel paging request at virtual address
  ffffd9c18eb05000
  of_find_matching_node_and_match+0x5c/0x1a0
  hantro_probe+0x2f4/0x7d0 [hantro_vpu]</p>
<p>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's later accessed during probe, causing a page fault.</p>
<p>The imx8mq_vpu_shared_resources is referenced from non-init code,
so keeping __initconst or __initconst_or_module here is wrong.</p>
<p>Drop the __initconst annotation and let it live in the normal .rodata
section.</p>
<p>A bug of __initconst called from regular non-init probe code
leading to bugs during probe deferrals or during unbind-bind cycles.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31573"/>
  </entry>
</feed>
