<?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>Mon, 05 Oct 2026 08:51:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12129</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12129</link>
      <description>bdu:2025-12129</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12129</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37938</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37938</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-2025-37938</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0463 — 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-0463</link>
      <description>certfr-2025-avi-0463</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0463</guid>
    </item>
    <item>
      <title>EUVD-2026-346866</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346866</link>
      <description>EUVD-2026-346866</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346866</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37938</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37938</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Verify event formats that have &amp;#34;%*p..&amp;#34;&lt;/p&gt;
&lt;p&gt;The trace event verifier checks the formats of trace events to make sure
that they do not point at memory that is not in the trace event itself or
in data that will never be freed. If an event references data that was
allocated when the event triggered and that same data is freed before the
event is read, then the kernel can crash by reading freed memory.&lt;/p&gt;
&lt;p&gt;The verifier runs at boot up (or module load) and scans the print formats
of the events and checks their arguments to make sure that dereferenced
pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it,
and that could be dangerous. Cover this case as well.&lt;/p&gt;
&lt;p&gt;Also add to the sample code a use case of &amp;#34;%*pbl&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;tracing: Verify event formats that have &amp;#34;%*p..&amp;#34;&lt;/p&gt;
&lt;p&gt;The trace event verifier checks the formats of trace events to make sure
that they do not point at memory that is not in the trace event itself or
in data that will never be freed. If an event references data that was
allocated when the event triggered and that same data is freed before the
event is read, then the kernel can crash by reading freed memory.&lt;/p&gt;
&lt;p&gt;The verifier runs at boot up (or module load) and scans the print formats
of the events and checks their arguments to make sure that dereferenced
pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it,
and that could be dangerous. Cover this case as well.&lt;/p&gt;
&lt;p&gt;Also add to the sample code a use case of &amp;#34;%*pbl&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37938</guid>
    </item>
    <item>
      <title>GHSA-r878-fwjf-3cg7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r878-fwjf-3cg7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Verify event formats that have &amp;#34;%*p..&amp;#34;&lt;/p&gt;
&lt;p&gt;The trace event verifier checks the formats of trace events to make sure
that they do not point at memory that is not in the trace event itself or
in data that will never be freed. If an event references data that was
allocated when the event triggered and that same data is freed before the
event is read, then the kernel can crash by reading freed memory.&lt;/p&gt;
&lt;p&gt;The verifier runs at boot up (or module load) and scans the print formats
of the events and checks their arguments to make sure that dereferenced
pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it,
and that could be dangerous. Cover this case as well.&lt;/p&gt;
&lt;p&gt;Also add to the sample code a use case of &amp;#34;%*pbl&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;tracing: Verify event formats that have &amp;#34;%*p..&amp;#34;&lt;/p&gt;
&lt;p&gt;The trace event verifier checks the formats of trace events to make sure
that they do not point at memory that is not in the trace event itself or
in data that will never be freed. If an event references data that was
allocated when the event triggered and that same data is freed before the
event is read, then the kernel can crash by reading freed memory.&lt;/p&gt;
&lt;p&gt;The verifier runs at boot up (or module load) and scans the print formats
of the events and checks their arguments to make sure that dereferenced
pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it,
and that could be dangerous. Cover this case as well.&lt;/p&gt;
&lt;p&gt;Also add to the sample code a use case of &amp;#34;%*pbl&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r878-fwjf-3cg7</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-37938 — tracing: Verify event formats that have "%*p.."</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37938</link>
      <description>msrc_CVE-2025-37938</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-37938</guid>
    </item>
    <item>
      <title>OESA-2025-1539 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1539</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;bpf: track changes_pkt_data property for global functions&lt;/p&gt;
&lt;p&gt;When processing calls to certain helpers, verifier invalidates all
packet pointers in a current state. For example, consider the
following program:&lt;/p&gt;
&lt;p&gt;__attribute__((__noinline__))
    long skb_pull_data(struct __sk_buff *sk, __u32 len)
    {
        return bpf_skb_pull_data(sk, len);
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int test_invalidate_checks(struct __sk_buff *sk)
    {
        int *p = (void *)(long)sk-&amp;amp;gt;data;
        if ((void *)(p + 1) &amp;amp;gt; (void *)(long)sk-&amp;amp;gt;data_end) return TCX_DROP;
        skb_pull_data(sk, 0);
        *p = 42;
        return TCX_PASS;
    }&lt;/p&gt;
&lt;p&gt;After a call to bpf_skb_pull_data() the pointer &amp;amp;apos;p&amp;amp;apos; can&amp;amp;apos;t be used
safely. See function filter.c:bpf_helper_changes_pkt_data() for a list
of such helpers.&lt;/p&gt;
&lt;p&gt;At the moment verifier invalidates packet pointers when processing
helper function calls, and does not traverse global sub-programs when
processing calls to global sub-programs. This means that calls to
helpers done from global sub-programs do not invalidate pointers in
the caller state. E.g. the program above is unsafe, but is not
rejected by verifier.&lt;/p&gt;
&lt;p&gt;This commit fixes the omission by computing field
bpf_subprog_info-&amp;amp;gt;changes_pkt_data for each sub-program before main
verification pass.
changes_pkt_data should be set if:
- subprogram…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;bpf: track changes_pkt_data property for global functions&lt;/p&gt;
&lt;p&gt;When processing calls to certain helpers, verifier invalidates all
packet pointers in a current state. For example, consider the
following program:&lt;/p&gt;
&lt;p&gt;__attribute__((__noinline__))
    long skb_pull_data(struct __sk_buff *sk, __u32 len)
    {
        return bpf_skb_pull_data(sk, len);
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int test_invalidate_checks(struct __sk_buff *sk)
    {
        int *p = (void *)(long)sk-&amp;amp;gt;data;
        if ((void *)(p + 1) &amp;amp;gt; (void *)(long)sk-&amp;amp;gt;data_end) return TCX_DROP;
        skb_pull_data(sk, 0);
        *p = 42;
        return TCX_PASS;
    }&lt;/p&gt;
&lt;p&gt;After a call to bpf_skb_pull_data() the pointer &amp;amp;apos;p&amp;amp;apos; can&amp;amp;apos;t be used
safely. See function filter.c:bpf_helper_changes_pkt_data() for a list
of such helpers.&lt;/p&gt;
&lt;p&gt;At the moment verifier invalidates packet pointers when processing
helper function calls, and does not traverse global sub-programs when
processing calls to global sub-programs. This means that calls to
helpers done from global sub-programs do not invalidate pointers in
the caller state. E.g. the program above is unsafe, but is not
rejected by verifier.&lt;/p&gt;
&lt;p&gt;This commit fixes the omission by computing field
bpf_subprog_info-&amp;amp;gt;changes_pkt_data for each sub-program before main
verification pass.
changes_pkt_data should be set if:
- subprogram…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1539</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-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:02249-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37938</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37938</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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Verify event formats that have &amp;#34;%*p..&amp;#34; The trace event verifier checks the formats of trace events to make sure that they do not point at memory that is not in the trace event itself or in data that will never be freed. If an event references data that was allocated when the event triggered and that same data is freed before the event is read, then the kernel can crash by reading freed memory. The verifier runs at boot up (or module load) and scans the print formats of the events and checks their arguments to make sure that dereferenced pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it, and that could be dangerous. Cover this case as well. Also add to the sample code a use case of &amp;#34;%*pbl&amp;#34;.&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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Verify event formats that have &amp;#34;%*p..&amp;#34; The trace event verifier checks the formats of trace events to make sure that they do not point at memory that is not in the trace event itself or in data that will never be freed. If an event references data that was allocated when the event triggered and that same data is freed before the event is read, then the kernel can crash by reading freed memory. The verifier runs at boot up (or module load) and scans the print formats of the events and checks their arguments to make sure that dereferenced pointers are safe. If the format uses &amp;#34;%*p..&amp;#34; the verifier will ignore it, and that could be dangerous. Cover this case as well. Also add to the sample code a use case of &amp;#34;%*pbl&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37938</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1114 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114</guid>
    </item>
  </channel>
</rss>
