<?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>Sun, 04 Oct 2026 04:01:57 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02781</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02781</link>
      <description>bdu:2026-02781</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02781</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-40107</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-40107</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-40107</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1010 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1010</link>
      <description>certfr-2025-avi-1010</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1010</guid>
    </item>
    <item>
      <title>EUVD-2026-314899</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314899</link>
      <description>EUVD-2026-314899</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314899</guid>
    </item>
    <item>
      <title>fkie_cve-2025-40107</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40107</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled&lt;/p&gt;
&lt;p&gt;This issue is similar to the vulnerability in the `mcp251x` driver,
which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from
sleep before interface was brought up&amp;#34;).&lt;/p&gt;
&lt;p&gt;In the `hi311x` driver, when the device resumes from sleep, the driver
schedules `priv-&amp;gt;restart_work`. However, if the network interface was
not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and
initialized, leading to a null pointer dereference.&lt;/p&gt;
&lt;p&gt;To fix this, we move the allocation and initialization of the workqueue
from the `hi3110_open` function to the `hi3110_can_probe` function.
This ensures that the workqueue is properly initialized before it is
used during device resume. And added logic to destroy the workqueue
in the error handling paths of `hi3110_can_probe` and in the
`hi3110_can_remove` function to prevent resource leaks.&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;can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled&lt;/p&gt;
&lt;p&gt;This issue is similar to the vulnerability in the `mcp251x` driver,
which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from
sleep before interface was brought up&amp;#34;).&lt;/p&gt;
&lt;p&gt;In the `hi311x` driver, when the device resumes from sleep, the driver
schedules `priv-&amp;gt;restart_work`. However, if the network interface was
not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and
initialized, leading to a null pointer dereference.&lt;/p&gt;
&lt;p&gt;To fix this, we move the allocation and initialization of the workqueue
from the `hi3110_open` function to the `hi3110_can_probe` function.
This ensures that the workqueue is properly initialized before it is
used during device resume. And added logic to destroy the workqueue
in the error handling paths of `hi3110_can_probe` and in the
`hi3110_can_remove` function to prevent resource leaks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-40107</guid>
    </item>
    <item>
      <title>GHSA-394x-fq64-jqf6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-394x-fq64-jqf6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled&lt;/p&gt;
&lt;p&gt;This issue is similar to the vulnerability in the `mcp251x` driver,
which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from
sleep before interface was brought up&amp;#34;).&lt;/p&gt;
&lt;p&gt;In the `hi311x` driver, when the device resumes from sleep, the driver
schedules `priv-&amp;gt;restart_work`. However, if the network interface was
not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and
initialized, leading to a null pointer dereference.&lt;/p&gt;
&lt;p&gt;To fix this, we move the allocation and initialization of the workqueue
from the `hi3110_open` function to the `hi3110_can_probe` function.
This ensures that the workqueue is properly initialized before it is
used during device resume. And added logic to destroy the workqueue
in the error handling paths of `hi3110_can_probe` and in the
`hi3110_can_remove` function to prevent resource leaks.&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;can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled&lt;/p&gt;
&lt;p&gt;This issue is similar to the vulnerability in the `mcp251x` driver,
which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from
sleep before interface was brought up&amp;#34;).&lt;/p&gt;
&lt;p&gt;In the `hi311x` driver, when the device resumes from sleep, the driver
schedules `priv-&amp;gt;restart_work`. However, if the network interface was
not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and
initialized, leading to a null pointer dereference.&lt;/p&gt;
&lt;p&gt;To fix this, we move the allocation and initialization of the workqueue
from the `hi3110_open` function to the `hi3110_can_probe` function.
This ensures that the workqueue is properly initialized before it is
used during device resume. And added logic to destroy the workqueue
in the error handling paths of `hi3110_can_probe` and in the
`hi3110_can_remove` function to prevent resource leaks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-394x-fq64-jqf6</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-40107 — can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-40107</link>
      <description>msrc_CVE-2025-40107</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-40107</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20172-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20172-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:20172-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4422-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4422-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:4422-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40107</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40107</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 223 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled This issue is similar to the vulnerability in the `mcp251x` driver, which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from sleep before interface was brought up&amp;#34;). In the `hi311x` driver, when the device resumes from sleep, the driver schedules `priv-&amp;gt;restart_work`. However, if the network interface was not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and initialized, leading to a null pointer dereference. To fix this, we move the allocation and initialization of the workqueue from the `hi3110_open` function to the `hi3110_can_probe` function. This ensures that the workqueue is properly initialized before it is used during device resume. And added logic to destroy the workqueue in the error handling paths of `hi3110_can_probe` and in the `hi3110_can_remove` function to prevent resource leaks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 223 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled This issue is similar to the vulnerability in the `mcp251x` driver, which was fixed in commit 03c427147b2d (&amp;#34;can: mcp251x: fix resume from sleep before interface was brought up&amp;#34;). In the `hi311x` driver, when the device resumes from sleep, the driver schedules `priv-&amp;gt;restart_work`. However, if the network interface was not previously enabled, the `priv-&amp;gt;wq` (workqueue) is not allocated and initialized, leading to a null pointer dereference. To fix this, we move the allocation and initialization of the workqueue from the `hi3110_open` function to the `hi3110_can_probe` function. This ensures that the workqueue is properly initialized before it is used during device resume. And added logic to destroy the workqueue in the error handling paths of `hi3110_can_probe` and in the `hi3110_can_remove` function to prevent resource leaks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40107</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2483 — Linux Kernel: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2483</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2483</guid>
    </item>
  </channel>
</rss>
