<?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:05:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03705</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03705</link>
      <description>bdu:2026-03705</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03705</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0212 — 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-0212</link>
      <description>certfr-2025-avi-0212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0212</guid>
    </item>
    <item>
      <title>EUVD-2026-310716</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310716</link>
      <description>EUVD-2026-310716</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310716</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49661</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49661</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&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: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49661</guid>
    </item>
    <item>
      <title>GHSA-fw87-5p3g-2r3p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fw87-5p3g-2r3p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&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: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fw87-5p3g-2r3p</guid>
    </item>
    <item>
      <title>OESA-2025-1282 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1282</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;ARM: davinci: da850-evm: Avoid NULL pointer dereference&lt;/p&gt;
&lt;p&gt;With newer versions of GCC, there is a panic in da850_evm_config_emac()
when booting multi_v5_defconfig in QEMU under the palmetto-bmc machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 00000020
pgd = (ptrval)
[00000020] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.0 #1
Hardware name: Generic DT based system
PC is at da850_evm_config_emac+0x1c/0x120
LR is at do_one_initcall+0x50/0x1e0&lt;/p&gt;
&lt;p&gt;The emac_pdata pointer in soc_info is NULL because davinci_soc_info only
gets populated on davinci machines but da850_evm_config_emac() is called
on all machines via device_initcall().&lt;/p&gt;
&lt;p&gt;Move the rmii_en assignment below the machine check so that it is only
dereferenced when running on a supported SoC.(CVE-2021-47631)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow&lt;/p&gt;
&lt;p&gt;Coverity complains of a possible buffer overflow. However,
given the &amp;amp;apos;static&amp;amp;apos; scope of nvidia_setup_i2c_bus() it looks
like that can&amp;amp;apos;t happen after examiniing the call sites.&lt;/p&gt;
&lt;p&gt;CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
1. fixed_size_dest: You might overrun the 48-character fixed-size string
  chan-&amp;amp;gt;adapter.name…&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;ARM: davinci: da850-evm: Avoid NULL pointer dereference&lt;/p&gt;
&lt;p&gt;With newer versions of GCC, there is a panic in da850_evm_config_emac()
when booting multi_v5_defconfig in QEMU under the palmetto-bmc machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 00000020
pgd = (ptrval)
[00000020] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.0 #1
Hardware name: Generic DT based system
PC is at da850_evm_config_emac+0x1c/0x120
LR is at do_one_initcall+0x50/0x1e0&lt;/p&gt;
&lt;p&gt;The emac_pdata pointer in soc_info is NULL because davinci_soc_info only
gets populated on davinci machines but da850_evm_config_emac() is called
on all machines via device_initcall().&lt;/p&gt;
&lt;p&gt;Move the rmii_en assignment below the machine check so that it is only
dereferenced when running on a supported SoC.(CVE-2021-47631)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow&lt;/p&gt;
&lt;p&gt;Coverity complains of a possible buffer overflow. However,
given the &amp;amp;apos;static&amp;amp;apos; scope of nvidia_setup_i2c_bus() it looks
like that can&amp;amp;apos;t happen after examiniing the call sites.&lt;/p&gt;
&lt;p&gt;CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
1. fixed_size_dest: You might overrun the 48-character fixed-size string
  chan-&amp;amp;gt;adapter.name…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1282</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0834-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0834-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:0834-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49661</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49661</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t actually free them. As a result, this may be leaking DMA memory that&amp;#39;s been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory leak&amp;#34;).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t actually free them. As a result, this may be leaking DMA memory that&amp;#39;s been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory leak&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49661</guid>
    </item>
  </channel>
</rss>
