<?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:34:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04535</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04535</link>
      <description>bdu:2026-04535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04535</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-46754</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-46754</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-46754</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0999 — 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-2024-avi-0999</link>
      <description>certfr-2024-avi-0999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</guid>
    </item>
    <item>
      <title>EUVD-2026-362946</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362946</link>
      <description>EUVD-2026-362946</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362946</guid>
    </item>
    <item>
      <title>fkie_cve-2024-46754</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-46754</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Remove tst_run from lwt_seg6local_prog_ops.&lt;/p&gt;
&lt;p&gt;The syzbot reported that the lwt_seg6 related BPF ops can be invoked
via bpf_test_run() without without entering input_action_end_bpf()
first.&lt;/p&gt;
&lt;p&gt;Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a
(&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the
per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
test case but each BPF function expects it.&lt;/p&gt;
&lt;p&gt;Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&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;bpf: Remove tst_run from lwt_seg6local_prog_ops.&lt;/p&gt;
&lt;p&gt;The syzbot reported that the lwt_seg6 related BPF ops can be invoked
via bpf_test_run() without without entering input_action_end_bpf()
first.&lt;/p&gt;
&lt;p&gt;Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a
(&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the
per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
test case but each BPF function expects it.&lt;/p&gt;
&lt;p&gt;Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-46754</guid>
    </item>
    <item>
      <title>GHSA-crwm-whhx-38v8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-crwm-whhx-38v8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Remove tst_run from lwt_seg6local_prog_ops.&lt;/p&gt;
&lt;p&gt;The syzbot reported that the lwt_seg6 related BPF ops can be invoked
via bpf_test_run() without without entering input_action_end_bpf()
first.&lt;/p&gt;
&lt;p&gt;Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a
(&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the
per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
test case but each BPF function expects it.&lt;/p&gt;
&lt;p&gt;Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&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;bpf: Remove tst_run from lwt_seg6local_prog_ops.&lt;/p&gt;
&lt;p&gt;The syzbot reported that the lwt_seg6 related BPF ops can be invoked
via bpf_test_run() without without entering input_action_end_bpf()
first.&lt;/p&gt;
&lt;p&gt;Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a
(&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the
per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
test case but each BPF function expects it.&lt;/p&gt;
&lt;p&gt;Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-crwm-whhx-38v8</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-46754 — bpf: Remove tst_run from lwt_seg6local_prog_ops.</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-46754</link>
      <description>msrc_CVE-2024-46754</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-46754</guid>
    </item>
    <item>
      <title>OESA-2024-2255 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2255</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/i915/gt: Cleanup partial engine discovery failures&#13;
&#13;
If we abort driver initialisation in the middle of gt/engine discovery,
some engines will be fully setup and some not. Those incompletely setup
engines only have &amp;amp;apos;engine-&amp;amp;gt;release == NULL&amp;amp;apos; and so will leak any of the
common objects allocated.&#13;
&#13;
v2:
 - Drop the destroy_pinned_context() helper for now.  It&amp;amp;apos;s not really
   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
f2fs: fix to avoid dirent corruption&#13;
&#13;
As Al reported in link[1]:&#13;
&#13;
f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;amp;&amp;amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&#13;
&#13;
You want correct inumber in the &amp;amp;quot;..&amp;amp;quot; link.  And cross-directory
rename does move the source to new parent, even if you&amp;amp;apos;d been asked
to leave a whiteout in the old place.&#13;
&#13;
[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&#13;
&#13;
With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;amp;quot;..&amp;amp;quot; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&#13;
&#13;
[ASSERT] (__chk_dots_dentries:1421)  --&amp;amp;gt; Bad inode number[0x4] for &amp;amp;apos;..&amp;amp;apos;, parent parent ino is [0…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/i915/gt: Cleanup partial engine discovery failures&#13;
&#13;
If we abort driver initialisation in the middle of gt/engine discovery,
some engines will be fully setup and some not. Those incompletely setup
engines only have &amp;amp;apos;engine-&amp;amp;gt;release == NULL&amp;amp;apos; and so will leak any of the
common objects allocated.&#13;
&#13;
v2:
 - Drop the destroy_pinned_context() helper for now.  It&amp;amp;apos;s not really
   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
f2fs: fix to avoid dirent corruption&#13;
&#13;
As Al reported in link[1]:&#13;
&#13;
f2fs_rename()
...
	if (old_dir != new_dir &amp;amp;amp;&amp;amp;amp; !whiteout)
		f2fs_set_link(old_inode, old_dir_entry,
					old_dir_page, new_dir);
	else
		f2fs_put_page(old_dir_page, 0);&#13;
&#13;
You want correct inumber in the &amp;amp;quot;..&amp;amp;quot; link.  And cross-directory
rename does move the source to new parent, even if you&amp;amp;apos;d been asked
to leave a whiteout in the old place.&#13;
&#13;
[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/&#13;
&#13;
With below testcase, it may cause dirent corruption, due to it missed
to call f2fs_set_link() to update &amp;amp;quot;..&amp;amp;quot; link to new directory.
- mkdir -p dir/foo
- renameat2 -w dir/foo bar&#13;
&#13;
[ASSERT] (__chk_dots_dentries:1421)  --&amp;amp;gt; Bad inode number[0x4] for &amp;amp;apos;..&amp;amp;apos;, parent parent ino is [0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2255</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3983-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-2024:3983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46754</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46754</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a (&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn&amp;#39;t work since it was introduced in commit 04d4b274e2a (&amp;#34;ipv6: sr: Add seg6local action End.BPF&amp;#34;). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46754</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2173 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</guid>
    </item>
  </channel>
</rss>
