<?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:47:50 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12000</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12000</link>
      <description>bdu:2025-12000</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12000</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38072</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38072</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-38072</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0587 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</link>
      <description>certfr-2025-avi-0587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</guid>
    </item>
    <item>
      <title>EUVD-2026-314413</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314413</link>
      <description>EUVD-2026-314413</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314413</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38072</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38072</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libnvdimm/labels: Fix divide error in nd_label_data_init()&lt;/p&gt;
&lt;p&gt;If a faulty CXL memory device returns a broken zero LSA size in its
memory device information (Identify Memory Device (Opcode 4000h), CXL
spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm
driver:&lt;/p&gt;
&lt;p&gt;Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
 RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm]&lt;/p&gt;
&lt;p&gt;Code and flow:&lt;/p&gt;
&lt;p&gt;1) CXL Command 4000h returns LSA size = 0
2) config_size is assigned to zero LSA size (CXL pmem driver):&lt;/p&gt;
&lt;p&gt;drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size,&lt;/p&gt;
&lt;p&gt;3) max_xfer is set to zero (nvdimm driver):&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size);&lt;/p&gt;
&lt;p&gt;4) A subsequent DIV_ROUND_UP() causes a division by zero:&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */
drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer,
drivers/nvdimm/label.c-                 config_size);&lt;/p&gt;
&lt;p&gt;Fix this by checking the config size parameter by extending an
existing check.&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;libnvdimm/labels: Fix divide error in nd_label_data_init()&lt;/p&gt;
&lt;p&gt;If a faulty CXL memory device returns a broken zero LSA size in its
memory device information (Identify Memory Device (Opcode 4000h), CXL
spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm
driver:&lt;/p&gt;
&lt;p&gt;Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
 RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm]&lt;/p&gt;
&lt;p&gt;Code and flow:&lt;/p&gt;
&lt;p&gt;1) CXL Command 4000h returns LSA size = 0
2) config_size is assigned to zero LSA size (CXL pmem driver):&lt;/p&gt;
&lt;p&gt;drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size,&lt;/p&gt;
&lt;p&gt;3) max_xfer is set to zero (nvdimm driver):&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size);&lt;/p&gt;
&lt;p&gt;4) A subsequent DIV_ROUND_UP() causes a division by zero:&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */
drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer,
drivers/nvdimm/label.c-                 config_size);&lt;/p&gt;
&lt;p&gt;Fix this by checking the config size parameter by extending an
existing check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38072</guid>
    </item>
    <item>
      <title>GHSA-6gcc-wg3c-rg44</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6gcc-wg3c-rg44</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libnvdimm/labels: Fix divide error in nd_label_data_init()&lt;/p&gt;
&lt;p&gt;If a faulty CXL memory device returns a broken zero LSA size in its
memory device information (Identify Memory Device (Opcode 4000h), CXL
spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm
driver:&lt;/p&gt;
&lt;p&gt;Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
 RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm]&lt;/p&gt;
&lt;p&gt;Code and flow:&lt;/p&gt;
&lt;p&gt;1) CXL Command 4000h returns LSA size = 0
2) config_size is assigned to zero LSA size (CXL pmem driver):&lt;/p&gt;
&lt;p&gt;drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size,&lt;/p&gt;
&lt;p&gt;3) max_xfer is set to zero (nvdimm driver):&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size);&lt;/p&gt;
&lt;p&gt;4) A subsequent DIV_ROUND_UP() causes a division by zero:&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */
drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer,
drivers/nvdimm/label.c-                 config_size);&lt;/p&gt;
&lt;p&gt;Fix this by checking the config size parameter by extending an
existing check.&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;libnvdimm/labels: Fix divide error in nd_label_data_init()&lt;/p&gt;
&lt;p&gt;If a faulty CXL memory device returns a broken zero LSA size in its
memory device information (Identify Memory Device (Opcode 4000h), CXL
spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm
driver:&lt;/p&gt;
&lt;p&gt;Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
 RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm]&lt;/p&gt;
&lt;p&gt;Code and flow:&lt;/p&gt;
&lt;p&gt;1) CXL Command 4000h returns LSA size = 0
2) config_size is assigned to zero LSA size (CXL pmem driver):&lt;/p&gt;
&lt;p&gt;drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size,&lt;/p&gt;
&lt;p&gt;3) max_xfer is set to zero (nvdimm driver):&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size);&lt;/p&gt;
&lt;p&gt;4) A subsequent DIV_ROUND_UP() causes a division by zero:&lt;/p&gt;
&lt;p&gt;drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */
drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer,
drivers/nvdimm/label.c-                 config_size);&lt;/p&gt;
&lt;p&gt;Fix this by checking the config size parameter by extending an
existing check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6gcc-wg3c-rg44</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38072 — libnvdimm/labels: Fix divide error in nd_label_data_init()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38072</link>
      <description>msrc_CVE-2025-38072</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38072</guid>
    </item>
    <item>
      <title>OESA-2025-1821 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1821</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;tty: n_gsm: add sanity check for gsm-&amp;amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-49940)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: opt3001: fix deadlock due to concurrent flag access&lt;/p&gt;
&lt;p&gt;The threaded IRQ function in this driver is reading the flag twice: once to
lock a mutex and once to unlock it. Even thou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;tty: n_gsm: add sanity check for gsm-&amp;amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-49940)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: opt3001: fix deadlock due to concurrent flag access&lt;/p&gt;
&lt;p&gt;The threaded IRQ function in this driver is reading the flag twice: once to
lock a mutex and once to unlock it. Even thou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1821</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-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:02249-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38072</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38072</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 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libnvdimm/labels: Fix divide error in nd_label_data_init() If a faulty CXL memory device returns a broken zero LSA size in its memory device information (Identify Memory Device (Opcode 4000h), CXL spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm driver:  Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI  RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm] Code and flow: 1) CXL Command 4000h returns LSA size = 0 2) config_size is assigned to zero LSA size (CXL pmem driver): drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size, 3) max_xfer is set to zero (nvdimm driver): drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size); 4) A subsequent DIV_ROUND_UP() causes a division by zero: drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */ drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer, drivers/nvdimm/label.c-                 config_size); Fix this by checking the config size parameter by extending an existing check.&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 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libnvdimm/labels: Fix divide error in nd_label_data_init() If a faulty CXL memory device returns a broken zero LSA size in its memory device information (Identify Memory Device (Opcode 4000h), CXL spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm driver:  Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI  RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm] Code and flow: 1) CXL Command 4000h returns LSA size = 0 2) config_size is assigned to zero LSA size (CXL pmem driver): drivers/cxl/pmem.c:             .config_size = mds-&amp;gt;lsa_size, 3) max_xfer is set to zero (nvdimm driver): drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd-&amp;gt;nsarea.max_xfer, config_size); 4) A subsequent DIV_ROUND_UP() causes a division by zero: drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */ drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer, drivers/nvdimm/label.c-                 config_size); Fix this by checking the config size parameter by extending an existing check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38072</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in 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-1350</guid>
    </item>
  </channel>
</rss>
