<?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 23:39:30 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13758</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13758</link>
      <description>bdu:2026-13758</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13758</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-54181</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54181</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-54181</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-312411</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312411</link>
      <description>EUVD-2026-312411</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312411</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54181</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54181</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix issue in verifying allow_ptr_leaks&lt;/p&gt;
&lt;p&gt;After we converted the capabilities of our networking-bpf program from
cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program
failed to start. Because it failed the bpf verifier, and the error log
is &amp;#34;R3 pointer comparison prohibited&amp;#34;.&lt;/p&gt;
&lt;p&gt;A simple reproducer as follows,&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;cls-ingress&amp;#34;)
int ingress(struct __sk_buff *skb)
{
	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr);&lt;/p&gt;
&lt;p&gt;if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end)
		return TC_ACT_STOLEN;
	return TC_ACT_OK;
}&lt;/p&gt;
&lt;p&gt;Per discussion with Yonghong and Alexei [1], comparison of two packet
pointers is not a pointer leak. This patch fixes it.&lt;/p&gt;
&lt;p&gt;Our local kernel is 6.1.y and we expect this fix to be backported to
6.1.y, so stable is CCed.&lt;/p&gt;
&lt;p&gt;[1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&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: Fix issue in verifying allow_ptr_leaks&lt;/p&gt;
&lt;p&gt;After we converted the capabilities of our networking-bpf program from
cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program
failed to start. Because it failed the bpf verifier, and the error log
is &amp;#34;R3 pointer comparison prohibited&amp;#34;.&lt;/p&gt;
&lt;p&gt;A simple reproducer as follows,&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;cls-ingress&amp;#34;)
int ingress(struct __sk_buff *skb)
{
	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr);&lt;/p&gt;
&lt;p&gt;if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end)
		return TC_ACT_STOLEN;
	return TC_ACT_OK;
}&lt;/p&gt;
&lt;p&gt;Per discussion with Yonghong and Alexei [1], comparison of two packet
pointers is not a pointer leak. This patch fixes it.&lt;/p&gt;
&lt;p&gt;Our local kernel is 6.1.y and we expect this fix to be backported to
6.1.y, so stable is CCed.&lt;/p&gt;
&lt;p&gt;[1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-54181</guid>
    </item>
    <item>
      <title>GHSA-6985-fmpm-h392</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6985-fmpm-h392</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix issue in verifying allow_ptr_leaks&lt;/p&gt;
&lt;p&gt;After we converted the capabilities of our networking-bpf program from
cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program
failed to start. Because it failed the bpf verifier, and the error log
is &amp;#34;R3 pointer comparison prohibited&amp;#34;.&lt;/p&gt;
&lt;p&gt;A simple reproducer as follows,&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;cls-ingress&amp;#34;)
int ingress(struct __sk_buff *skb)
{
	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr);&lt;/p&gt;
&lt;p&gt;if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end)
		return TC_ACT_STOLEN;
	return TC_ACT_OK;
}&lt;/p&gt;
&lt;p&gt;Per discussion with Yonghong and Alexei [1], comparison of two packet
pointers is not a pointer leak. This patch fixes it.&lt;/p&gt;
&lt;p&gt;Our local kernel is 6.1.y and we expect this fix to be backported to
6.1.y, so stable is CCed.&lt;/p&gt;
&lt;p&gt;[1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&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: Fix issue in verifying allow_ptr_leaks&lt;/p&gt;
&lt;p&gt;After we converted the capabilities of our networking-bpf program from
cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program
failed to start. Because it failed the bpf verifier, and the error log
is &amp;#34;R3 pointer comparison prohibited&amp;#34;.&lt;/p&gt;
&lt;p&gt;A simple reproducer as follows,&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;cls-ingress&amp;#34;)
int ingress(struct __sk_buff *skb)
{
	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr);&lt;/p&gt;
&lt;p&gt;if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end)
		return TC_ACT_STOLEN;
	return TC_ACT_OK;
}&lt;/p&gt;
&lt;p&gt;Per discussion with Yonghong and Alexei [1], comparison of two packet
pointers is not a pointer leak. This patch fixes it.&lt;/p&gt;
&lt;p&gt;Our local kernel is 6.1.y and we expect this fix to be backported to
6.1.y, so stable is CCed.&lt;/p&gt;
&lt;p&gt;[1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6985-fmpm-h392</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0278-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-2026:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54181</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54181</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 171 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix issue in verifying allow_ptr_leaks After we converted the capabilities of our networking-bpf program from cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program failed to start. Because it failed the bpf verifier, and the error log is &amp;#34;R3 pointer comparison prohibited&amp;#34;. A simple reproducer as follows, SEC(&amp;#34;cls-ingress&amp;#34;) int ingress(struct __sk_buff *skb) { 	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr); 	if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end) 		return TC_ACT_STOLEN; 	return TC_ACT_OK; } Per discussion with Yonghong and Alexei [1], comparison of two packet pointers is not a pointer leak. This patch fixes it. Our local kernel is 6.1.y and we expect this fix to be backported to 6.1.y, so stable is CCed. [1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&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 171 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix issue in verifying allow_ptr_leaks After we converted the capabilities of our networking-bpf program from cap_sys_admin to cap_net_admin+cap_bpf, our networking-bpf program failed to start. Because it failed the bpf verifier, and the error log is &amp;#34;R3 pointer comparison prohibited&amp;#34;. A simple reproducer as follows, SEC(&amp;#34;cls-ingress&amp;#34;) int ingress(struct __sk_buff *skb) { 	struct iphdr *iph = (void *)(long)skb-&amp;gt;data + sizeof(struct ethhdr); 	if ((long)(iph + 1) &amp;gt; (long)skb-&amp;gt;data_end) 		return TC_ACT_STOLEN; 	return TC_ACT_OK; } Per discussion with Yonghong and Alexei [1], comparison of two packet pointers is not a pointer leak. This patch fixes it. Our local kernel is 6.1.y and we expect this fix to be backported to 6.1.y, so stable is CCed. [1]. https://lore.kernel.org/bpf/CAADnVQ+Nmspr7Si+pxWn8zkE7hX-7s93ugwC+94aXSy4uQ9vBg@mail.gmail.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54181</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2941 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</link>
      <description>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</guid>
    </item>
  </channel>
</rss>
