<?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 19:59:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12278</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12278</link>
      <description>bdu:2025-12278</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12278</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37839</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37839</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-37839</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0463 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0463</link>
      <description>certfr-2025-avi-0463</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0463</guid>
    </item>
    <item>
      <title>EUVD-2026-320819</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320819</link>
      <description>EUVD-2026-320819</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320819</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37839</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37839</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: remove wrong sb-&amp;gt;s_sequence check&lt;/p&gt;
&lt;p&gt;Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by
sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a
valid transaction ID so the check can spuriously trigger. Remove the
invalid WARN_ON.&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;jbd2: remove wrong sb-&amp;gt;s_sequence check&lt;/p&gt;
&lt;p&gt;Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by
sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a
valid transaction ID so the check can spuriously trigger. Remove the
invalid WARN_ON.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37839</guid>
    </item>
    <item>
      <title>GHSA-8rhx-6jcw-6ghv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8rhx-6jcw-6ghv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: remove wrong sb-&amp;gt;s_sequence check&lt;/p&gt;
&lt;p&gt;Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by
sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a
valid transaction ID so the check can spuriously trigger. Remove the
invalid WARN_ON.&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;jbd2: remove wrong sb-&amp;gt;s_sequence check&lt;/p&gt;
&lt;p&gt;Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by
sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a
valid transaction ID so the check can spuriously trigger. Remove the
invalid WARN_ON.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8rhx-6jcw-6ghv</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-37839 — jbd2: remove wrong sb-&gt;s_sequence check</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37839</link>
      <description>msrc_CVE-2025-37839</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-37839</guid>
    </item>
    <item>
      <title>OESA-2025-1541 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1541</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mISDN: fix possible memory leak in mISDN_dsp_element_register()&lt;/p&gt;
&lt;p&gt;Afer commit 1fa5ae857bb1 (&amp;amp;quot;driver core: get rid of struct device&amp;amp;apos;s
bus_id string array&amp;amp;quot;), the name of device is allocated dynamically,
use put_device() to give up the reference, so that the name can be
freed in kobject_cleanup() when the refcount is 0.&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;entry&amp;amp;apos; is going to be freed in mISDN_dsp_dev_release(), so the
kfree() is removed. list_del() is called in mISDN_dsp_dev_release(),
so it need be initialized.(CVE-2022-49821)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map&lt;/p&gt;
&lt;p&gt;Here is the BUG report by KASAN about null pointer dereference:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: null-ptr-deref in strcmp+0x2e/0x50
Read of size 1 at addr 0000000000000000 by task python3/2640
Call Trace:
 strcmp
 __of_find_property
 of_find_property
 pinctrl_dt_to_map&lt;/p&gt;
&lt;p&gt;kasprintf() would return NULL pointer when kmalloc() fail to allocate.
So directly return ENOMEM, if kasprintf() return NULL pointer.(CVE-2022-49832)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udf: Fix a slab-out-of-bounds write bug in udf_find_entry()&lt;/p&gt;
&lt;p&gt;Syzbot reported a slab-out-of-bounds Write bug:&lt;/p&gt;
&lt;p&gt;loop0: detected capacity change from 0 to 2048
============================================================…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mISDN: fix possible memory leak in mISDN_dsp_element_register()&lt;/p&gt;
&lt;p&gt;Afer commit 1fa5ae857bb1 (&amp;amp;quot;driver core: get rid of struct device&amp;amp;apos;s
bus_id string array&amp;amp;quot;), the name of device is allocated dynamically,
use put_device() to give up the reference, so that the name can be
freed in kobject_cleanup() when the refcount is 0.&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;entry&amp;amp;apos; is going to be freed in mISDN_dsp_dev_release(), so the
kfree() is removed. list_del() is called in mISDN_dsp_dev_release(),
so it need be initialized.(CVE-2022-49821)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map&lt;/p&gt;
&lt;p&gt;Here is the BUG report by KASAN about null pointer dereference:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: null-ptr-deref in strcmp+0x2e/0x50
Read of size 1 at addr 0000000000000000 by task python3/2640
Call Trace:
 strcmp
 __of_find_property
 of_find_property
 pinctrl_dt_to_map&lt;/p&gt;
&lt;p&gt;kasprintf() would return NULL pointer when kmalloc() fail to allocate.
So directly return ENOMEM, if kasprintf() return NULL pointer.(CVE-2022-49832)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udf: Fix a slab-out-of-bounds write bug in udf_find_entry()&lt;/p&gt;
&lt;p&gt;Syzbot reported a slab-out-of-bounds Write bug:&lt;/p&gt;
&lt;p&gt;loop0: detected capacity change from 0 to 2048
============================================================…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1541</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01964-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01964-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:01964-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37839</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37839</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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-&amp;gt;s_sequence check Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.&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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-&amp;gt;s_sequence check Journal emptiness is not determined by sb-&amp;gt;s_sequence == 0 but rather by sb-&amp;gt;s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37839</guid>
    </item>
  </channel>
</rss>
