<?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>Sat, 03 Oct 2026 09:02:30 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04491</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04491</link>
      <description>bdu:2025-04491</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04491</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-50133</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-50133</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-2024-50133</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0002 — 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-0002</link>
      <description>certfr-2025-avi-0002</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0002</guid>
    </item>
    <item>
      <title>EUVD-2026-313500</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313500</link>
      <description>EUVD-2026-313500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313500</guid>
    </item>
    <item>
      <title>fkie_cve-2024-50133</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-50133</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO&lt;/p&gt;
&lt;p&gt;Not all tasks have a vDSO mapped, for example kthreads never do. If such
a task ever ends up calling stack_top(), it will derefence the NULL vdso
pointer and crash.&lt;/p&gt;
&lt;p&gt;This can for example happen when using kunit:&lt;/p&gt;
&lt;p&gt;[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8
	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220
	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c
	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c
	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8
	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c
	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184
	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48
	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4
	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&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;LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO&lt;/p&gt;
&lt;p&gt;Not all tasks have a vDSO mapped, for example kthreads never do. If such
a task ever ends up calling stack_top(), it will derefence the NULL vdso
pointer and crash.&lt;/p&gt;
&lt;p&gt;This can for example happen when using kunit:&lt;/p&gt;
&lt;p&gt;[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8
	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220
	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c
	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c
	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8
	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c
	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184
	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48
	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4
	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-50133</guid>
    </item>
    <item>
      <title>GHSA-x3fm-x4jg-jw2h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x3fm-x4jg-jw2h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO&lt;/p&gt;
&lt;p&gt;Not all tasks have a vDSO mapped, for example kthreads never do. If such
a task ever ends up calling stack_top(), it will derefence the NULL vdso
pointer and crash.&lt;/p&gt;
&lt;p&gt;This can for example happen when using kunit:&lt;/p&gt;
&lt;p&gt;[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8
	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220
	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c
	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c
	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8
	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c
	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184
	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48
	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4
	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&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;LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO&lt;/p&gt;
&lt;p&gt;Not all tasks have a vDSO mapped, for example kthreads never do. If such
a task ever ends up calling stack_top(), it will derefence the NULL vdso
pointer and crash.&lt;/p&gt;
&lt;p&gt;This can for example happen when using kunit:&lt;/p&gt;
&lt;p&gt;[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8
	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220
	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c
	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c
	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8
	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c
	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184
	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48
	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4
	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x3fm-x4jg-jw2h</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-50133 — LoongArch: Don't crash in stack_top() for tasks without vDSO</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-50133</link>
      <description>msrc_CVE-2024-50133</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-50133</guid>
    </item>
    <item>
      <title>OESA-2024-2424 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2424</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
pinctrl: single: fix potential NULL dereference in pcs_get_function()&#13;
&#13;
pinmux_generic_get_function() can return NULL and the pointer &amp;amp;apos;function&amp;amp;apos;
was dereferenced without checking against NULL. Add checking of pointer
&amp;amp;apos;function&amp;amp;apos; in pcs_get_function().&#13;
&#13;
Found by code review.(CVE-2024-46685)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thunderbolt: Mark XDomain as unplugged when router is removed&#13;
&#13;
I noticed that when we do discrete host router NVM upgrade and it gets
hot-removed from the PCIe side as a result of NVM firmware authentication,
if there is another host connected with enabled paths we hang in tearing
them down. This is due to fact that the Thunderbolt networking driver
also tries to cleanup the paths and ends up blocking in
tb_disconnect_xdomain_paths() waiting for the domain lock.&#13;
&#13;
However, at this point we already cleaned the paths in tb_stop() so
there is really no need for tb_disconnect_xdomain_paths() to do that
anymore. Furthermore it already checks if the XDomain is unplugged and
bails out early so take advantage of that and mark the XDomain as
unplugged when we remove the parent router.(CVE-2024-46702)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]&#13;
&#13;
[WHY &amp;amp;amp;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
pinctrl: single: fix potential NULL dereference in pcs_get_function()&#13;
&#13;
pinmux_generic_get_function() can return NULL and the pointer &amp;amp;apos;function&amp;amp;apos;
was dereferenced without checking against NULL. Add checking of pointer
&amp;amp;apos;function&amp;amp;apos; in pcs_get_function().&#13;
&#13;
Found by code review.(CVE-2024-46685)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thunderbolt: Mark XDomain as unplugged when router is removed&#13;
&#13;
I noticed that when we do discrete host router NVM upgrade and it gets
hot-removed from the PCIe side as a result of NVM firmware authentication,
if there is another host connected with enabled paths we hang in tearing
them down. This is due to fact that the Thunderbolt networking driver
also tries to cleanup the paths and ends up blocking in
tb_disconnect_xdomain_paths() waiting for the domain lock.&#13;
&#13;
However, at this point we already cleaned the paths in tb_stop() so
there is really no need for tb_disconnect_xdomain_paths() to do that
anymore. Furthermore it already checks if the XDomain is unplugged and
bails out early so take advantage of that and mark the XDomain as
unplugged when we remove the parent router.(CVE-2024-46702)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]&#13;
&#13;
[WHY &amp;amp;amp;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2424</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50133</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50133</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO Not all tasks have a vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL vdso pointer and crash. This can for example happen when using kunit: 	[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8 	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220 	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c 	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c 	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8 	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c 	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184 	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48 	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4 	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Don&amp;#39;t crash in stack_top() for tasks without vDSO Not all tasks have a vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL vdso pointer and crash. This can for example happen when using kunit: 	[&amp;lt;9000000000203874&amp;gt;] stack_top+0x58/0xa8 	[&amp;lt;90000000002956cc&amp;gt;] arch_pick_mmap_layout+0x164/0x220 	[&amp;lt;90000000003c284c&amp;gt;] kunit_vm_mmap_init+0x108/0x12c 	[&amp;lt;90000000003c1fbc&amp;gt;] __kunit_add_resource+0x38/0x8c 	[&amp;lt;90000000003c2704&amp;gt;] kunit_vm_mmap+0x88/0xc8 	[&amp;lt;9000000000410b14&amp;gt;] usercopy_test_init+0xbc/0x25c 	[&amp;lt;90000000003c1db4&amp;gt;] kunit_try_run_case+0x5c/0x184 	[&amp;lt;90000000003c3d54&amp;gt;] kunit_generic_run_threadfn_adapter+0x24/0x48 	[&amp;lt;900000000022e4bc&amp;gt;] kthread+0xc8/0xd4 	[&amp;lt;9000000000200ce8&amp;gt;] ret_from_kernel_thread+0xc/0xa4&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50133</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3339 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3339</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3339</guid>
    </item>
  </channel>
</rss>
