<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 16:03:21 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-31573 — CVE-2026-31573 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31573</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-31573</guid>
    </item>
    <item>
      <title>EUVD-2026-315631</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315631</link>
      <description>EUVD-2026-315631</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315631</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31573</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31573</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-31573</guid>
    </item>
    <item>
      <title>GHSA-2pqc-qvpf-mwm4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2pqc-qvpf-mwm4</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-2pqc-qvpf-mwm4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31573</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31573</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: verisilicon: Fix kernel panic due to __initconst misuse Fix a kernel panic when probing the driver as a module:   Unable to handle kernel paging request at virtual address   ffffd9c18eb05000   of_find_matching_node_and_match+0x5c/0x1a0   hantro_probe+0x2f4/0x7d0 [hantro_vpu] 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. The imx8mq_vpu_shared_resources is referenced from non-init code, so keeping __initconst or __initconst_or_module here is wrong. Drop the __initconst annotation and let it live in the normal .rodata section. 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: verisilicon: Fix kernel panic due to __initconst misuse Fix a kernel panic when probing the driver as a module:   Unable to handle kernel paging request at virtual address   ffffd9c18eb05000   of_find_matching_node_and_match+0x5c/0x1a0   hantro_probe+0x2f4/0x7d0 [hantro_vpu] 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. The imx8mq_vpu_shared_resources is referenced from non-init code, so keeping __initconst or __initconst_or_module here is wrong. Drop the __initconst annotation and let it live in the normal .rodata section. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31573</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1279 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279</guid>
    </item>
  </channel>
</rss>
