<?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>Sun, 04 Oct 2026 12:11:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12023</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12023</link>
      <description>bdu:2025-12023</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12023</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37818</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37818</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-37818</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-314259</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314259</link>
      <description>EUVD-2026-314259</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314259</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37818</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37818</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&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: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37818</guid>
    </item>
    <item>
      <title>GHSA-4q4q-jv3m-fqjr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4q4q-jv3m-fqjr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&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: Return NULL from huge_pte_offset() for invalid PMD&lt;/p&gt;
&lt;p&gt;LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot
even if the underlying entry points to invalid_pte_table (indicating no
mapping). Callers like smaps_hugetlb_range() fetch this invalid entry
value (the address of invalid_pte_table) via this pointer.&lt;/p&gt;
&lt;p&gt;The generic is_swap_pte() check then incorrectly identifies this address
as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present()
&amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a
coincidental match by is_migration_entry() on the address bits, leads to
kernel crashes in pfn_swap_entry_to_page().&lt;/p&gt;
&lt;p&gt;Fix this at the architecture level by modifying huge_pte_offset() to
check the PMD entry&amp;#39;s content using pmd_none() before returning. If the
entry is invalid (i.e., it points to invalid_pte_table), return NULL
instead of the pointer to the slot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4q4q-jv3m-fqjr</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-37818 — LoongArch: Return NULL from huge_pte_offset() for invalid PMD</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37818</link>
      <description>msrc_CVE-2025-37818</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-37818</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>UBUNTU-CVE-2025-37818</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37818</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.14, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.14&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Return NULL from huge_pte_offset() for invalid PMD LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot even if the underlying entry points to invalid_pte_table (indicating no mapping). Callers like smaps_hugetlb_range() fetch this invalid entry value (the address of invalid_pte_table) via this pointer. The generic is_swap_pte() check then incorrectly identifies this address as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present() &amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a coincidental match by is_migration_entry() on the address bits, leads to kernel crashes in pfn_swap_entry_to_page(). Fix this at the architecture level by modifying huge_pte_offset() to check the PMD entry&amp;#39;s content using pmd_none() before returning. If the entry is invalid (i.e., it points to invalid_pte_table), return NULL instead of the pointer to the slot.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.14, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.14&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Return NULL from huge_pte_offset() for invalid PMD LoongArch&amp;#39;s huge_pte_offset() currently returns a pointer to a PMD slot even if the underlying entry points to invalid_pte_table (indicating no mapping). Callers like smaps_hugetlb_range() fetch this invalid entry value (the address of invalid_pte_table) via this pointer. The generic is_swap_pte() check then incorrectly identifies this address as a swap entry on LoongArch, because it satisfies the &amp;#34;!pte_present() &amp;amp;&amp;amp; !pte_none()&amp;#34; conditions. This misinterpretation, combined with a coincidental match by is_migration_entry() on the address bits, leads to kernel crashes in pfn_swap_entry_to_page(). Fix this at the architecture level by modifying huge_pte_offset() to check the PMD entry&amp;#39;s content using pmd_none() before returning. If the entry is invalid (i.e., it points to invalid_pte_table), return NULL instead of the pointer to the slot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37818</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0975 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0975</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0975</guid>
    </item>
  </channel>
</rss>
