<?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>Fri, 02 Oct 2026 19:53:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12977</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12977</link>
      <description>bdu:2025-12977</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12977</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53446</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53446</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53446</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>EUVD-2026-312063</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312063</link>
      <description>EUVD-2026-312063</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312063</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53446</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53446</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function
0.  Previously we retained that pointer when removing function 0, and
subsequent ASPM policy changes dereferenced it, resulting in a
use-after-free warning from KASAN, e.g.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500
  Call Trace:
   kasan_report+0xae/0xe0
   pcie_config_aspm_link+0x42d/0x500
   pcie_aspm_set_policy+0x8e/0x1a0
   param_attr_store+0x162/0x2c0
   module_attr_store+0x3e/0x80&lt;/p&gt;
&lt;p&gt;PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM
Control value in all functions of multi-function devices.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&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;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function
0.  Previously we retained that pointer when removing function 0, and
subsequent ASPM policy changes dereferenced it, resulting in a
use-after-free warning from KASAN, e.g.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500
  Call Trace:
   kasan_report+0xae/0xe0
   pcie_config_aspm_link+0x42d/0x500
   pcie_aspm_set_policy+0x8e/0x1a0
   param_attr_store+0x162/0x2c0
   module_attr_store+0x3e/0x80&lt;/p&gt;
&lt;p&gt;PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM
Control value in all functions of multi-function devices.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53446</guid>
    </item>
    <item>
      <title>GHSA-62j3-36wr-4gw5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-62j3-36wr-4gw5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function
0.  Previously we retained that pointer when removing function 0, and
subsequent ASPM policy changes dereferenced it, resulting in a
use-after-free warning from KASAN, e.g.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500
  Call Trace:
   kasan_report+0xae/0xe0
   pcie_config_aspm_link+0x42d/0x500
   pcie_aspm_set_policy+0x8e/0x1a0
   param_attr_store+0x162/0x2c0
   module_attr_store+0x3e/0x80&lt;/p&gt;
&lt;p&gt;PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM
Control value in all functions of multi-function devices.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&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;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function
0.  Previously we retained that pointer when removing function 0, and
subsequent ASPM policy changes dereferenced it, resulting in a
use-after-free warning from KASAN, e.g.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500
  Call Trace:
   kasan_report+0xae/0xe0
   pcie_config_aspm_link+0x42d/0x500
   pcie_aspm_set_policy+0x8e/0x1a0
   param_attr_store+0x162/0x2c0
   module_attr_store+0x3e/0x80&lt;/p&gt;
&lt;p&gt;PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM
Control value in all functions of multi-function devices.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-62j3-36wr-4gw5</guid>
    </item>
    <item>
      <title>OESA-2025-2659 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2659</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;misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()&lt;/p&gt;
&lt;p&gt;If device_register() returns error in tifm_7xx1_switch_media(),
name of kobject which is allocated in dev_set_name() called in device_add()
is leaked.&lt;/p&gt;
&lt;p&gt;Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.(CVE-2022-50349)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;amp;quot;systemd-udevd&amp;amp;quot;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;amp;lt;0000000034783f26&amp;amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;amp;lt;00000000748188f2&amp;amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;amp;lt;00000000ab0743e8&amp;amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;amp;lt;000000006c0ffb13&amp;amp;gt;] kvasprintf+0x8c/0x118
    [&amp;amp;lt;00000000…&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;misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()&lt;/p&gt;
&lt;p&gt;If device_register() returns error in tifm_7xx1_switch_media(),
name of kobject which is allocated in dev_set_name() called in device_add()
is leaked.&lt;/p&gt;
&lt;p&gt;Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.(CVE-2022-50349)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;amp;quot;systemd-udevd&amp;amp;quot;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;amp;lt;0000000034783f26&amp;amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;amp;lt;00000000748188f2&amp;amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;amp;lt;00000000ab0743e8&amp;amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;amp;lt;000000006c0ffb13&amp;amp;gt;] kvasprintf+0x8c/0x118
    [&amp;amp;lt;00000000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2659</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53446</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53446</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function 0.  Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.:   # echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove   # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy   BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500   Call Trace:    kasan_report+0xae/0xe0    pcie_config_aspm_link+0x42d/0x500    pcie_aspm_set_policy+0x8e/0x1a0    param_attr_store+0x162/0x2c0    module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment]&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state-&amp;gt;downstream is a pointer to the pci_dev of function 0.  Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.:   # echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove   # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy   BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500   Call Trace:    kasan_report+0xae/0xe0    pcie_config_aspm_link+0x42d/0x500    pcie_aspm_set_policy+0x8e/0x1a0    param_attr_store+0x162/0x2c0    module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53446</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2092 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</guid>
    </item>
  </channel>
</rss>
