<?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 20:31:17 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01805</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01805</link>
      <description>bdu:2025-01805</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01805</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-45009</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-45009</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-45009</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>cnvd-2024-39478</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-39478</link>
      <description>cnvd-2024-39478</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-39478</guid>
    </item>
    <item>
      <title>EUVD-2026-346072</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346072</link>
      <description>EUVD-2026-346072</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346072</guid>
    </item>
    <item>
      <title>fkie_cve-2024-45009</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-45009</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&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;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-45009</guid>
    </item>
    <item>
      <title>GHSA-rhqc-rfxh-qj7g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rhqc-rfxh-qj7g</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&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;mptcp: pm: only decrement add_addr_accepted for MPJ req&lt;/p&gt;
&lt;p&gt;Adding the following warning ...&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0)&lt;/p&gt;
&lt;p&gt;... before decrementing the add_addr_accepted counter helped to find a
bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the
mptcp_join.sh selftest.&lt;/p&gt;
&lt;p&gt;Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the
subflow closure. Before this patch, and upon the reception of the
RM_ADDR, the other peer will then try to decrement this
add_addr_accepted. That&amp;#39;s not correct because the attached subflows have
not been created upon the reception of an ADD_ADDR.&lt;/p&gt;
&lt;p&gt;A way to solve that is to decrement the counter only if the attached
subflow was an MP_JOIN to a remote id that was not 0, and initiated by
the host receiving the RM_ADDR.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rhqc-rfxh-qj7g</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-45009 — mptcp: pm: only decrement add_addr_accepted for MPJ req</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-45009</link>
      <description>msrc_CVE-2024-45009</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-45009</guid>
    </item>
    <item>
      <title>OESA-2024-2219 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2219</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()&#13;
&#13;
set_memory_rox() can fail, leaving memory unprotected.&#13;
&#13;
Check return and bail out when bpf_jit_binary_lock_ro() returns
an error.(CVE-2024-42067)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
sysctl: always initialize i_uid/i_gid&#13;
&#13;
Always initialize i_uid/i_gid inside the sysfs core so set_ownership()
can safely skip setting them.&#13;
&#13;
Commit 5ec27ec735ba (&amp;amp;quot;fs/proc/proc_sysctl.c: fix the default values of
i_uid/i_gid on /proc/sys inodes.&amp;amp;quot;) added defaults for i_uid/i_gid when
set_ownership() was not implemented. It also missed adjusting
net_ctl_set_ownership() to use the same default values in case the
computation of a better value failed.(CVE-2024-42312)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
parisc: fix a possible DMA corruption&#13;
&#13;
ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
possible that two unrelated 16-byte allocations share a cache line. If
one of these allocations is written using DMA and the other is written
using cached write, the value that was written with DMA may be
corrupted.&#13;
&#13;
This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
that&amp;amp;apos;s the largest possible cache line size.&#13;
&#13;
As different parisc microarchitectur…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()&#13;
&#13;
set_memory_rox() can fail, leaving memory unprotected.&#13;
&#13;
Check return and bail out when bpf_jit_binary_lock_ro() returns
an error.(CVE-2024-42067)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
sysctl: always initialize i_uid/i_gid&#13;
&#13;
Always initialize i_uid/i_gid inside the sysfs core so set_ownership()
can safely skip setting them.&#13;
&#13;
Commit 5ec27ec735ba (&amp;amp;quot;fs/proc/proc_sysctl.c: fix the default values of
i_uid/i_gid on /proc/sys inodes.&amp;amp;quot;) added defaults for i_uid/i_gid when
set_ownership() was not implemented. It also missed adjusting
net_ctl_set_ownership() to use the same default values in case the
computation of a better value failed.(CVE-2024-42312)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
parisc: fix a possible DMA corruption&#13;
&#13;
ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
possible that two unrelated 16-byte allocations share a cache line. If
one of these allocations is written using DMA and the other is written
using cached write, the value that was written with DMA may be
corrupted.&#13;
&#13;
This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
that&amp;amp;apos;s the largest possible cache line size.&#13;
&#13;
As different parisc microarchitectur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2219</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-2025:0784-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0784-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:0784-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-45009</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45009</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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only decrement add_addr_accepted for MPJ req Adding the following warning ...   WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0) ... before decrementing the add_addr_accepted counter helped to find a bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the mptcp_join.sh selftest. Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That&amp;#39;s not correct because the attached subflows have not been created upon the reception of an ADD_ADDR. A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR.&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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only decrement add_addr_accepted for MPJ req Adding the following warning ...   WARN_ON_ONCE(msk-&amp;gt;pm.add_addr_accepted == 0) ... before decrementing the add_addr_accepted counter helped to find a bug when running the &amp;#34;remove single subflow&amp;#34; subtest from the mptcp_join.sh selftest. Removing a &amp;#39;subflow&amp;#39; endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That&amp;#39;s not correct because the attached subflows have not been created upon the reception of an ADD_ADDR. A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45009</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2124 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2124</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-2124</guid>
    </item>
  </channel>
</rss>
