<?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 11:13:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02683</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02683</link>
      <description>bdu:2026-02683</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02683</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39909</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39909</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-39909</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0894 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894</link>
      <description>certfr-2025-avi-0894</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894</guid>
    </item>
    <item>
      <title>EUVD-2026-314821</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314821</link>
      <description>EUVD-2026-314821</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314821</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39909</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39909</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters
application&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on
user-configured parameters during application, which may lead to
division-by-zero errors.&lt;/p&gt;
&lt;p&gt;Avoid the divide-by-zero by adding validation checks when DAMON modules
attempt to apply the parameters.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either
&amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may
lead to division-by-zero errors.  Fix it by directly returning -EINVAL
when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already
required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(),
only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&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;mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters
application&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on
user-configured parameters during application, which may lead to
division-by-zero errors.&lt;/p&gt;
&lt;p&gt;Avoid the divide-by-zero by adding validation checks when DAMON modules
attempt to apply the parameters.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either
&amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may
lead to division-by-zero errors.  Fix it by directly returning -EINVAL
when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already
required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(),
only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39909</guid>
    </item>
    <item>
      <title>GHSA-jh5r-m3qc-3584</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jh5r-m3qc-3584</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters
application&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on
user-configured parameters during application, which may lead to
division-by-zero errors.&lt;/p&gt;
&lt;p&gt;Avoid the divide-by-zero by adding validation checks when DAMON modules
attempt to apply the parameters.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either
&amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may
lead to division-by-zero errors.  Fix it by directly returning -EINVAL
when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already
required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(),
only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&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;mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters
application&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on
user-configured parameters during application, which may lead to
division-by-zero errors.&lt;/p&gt;
&lt;p&gt;Avoid the divide-by-zero by adding validation checks when DAMON modules
attempt to apply the parameters.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either
&amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may
lead to division-by-zero errors.  Fix it by directly returning -EINVAL
when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already
required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(),
only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jh5r-m3qc-3584</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-39909 — mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-39909</link>
      <description>msrc_CVE-2025-39909</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-39909</guid>
    </item>
    <item>
      <title>OESA-2025-2695 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2695</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2695</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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/opensuse-su-2025:20081-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21074-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21074-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:21074-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39909</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39909</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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters() Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters application&amp;#34;. DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on user-configured parameters during application, which may lead to division-by-zero errors. Avoid the divide-by-zero by adding validation checks when DAMON modules attempt to apply the parameters. This patch (of 2): During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either &amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may lead to division-by-zero errors.  Fix it by directly returning -EINVAL when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(), only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters() Patch series &amp;#34;mm/damon: avoid divide-by-zero in DAMON module&amp;#39;s parameters application&amp;#34;. DAMON&amp;#39;s RECLAIM and LRU_SORT modules perform no validation on user-configured parameters during application, which may lead to division-by-zero errors. Avoid the divide-by-zero by adding validation checks when DAMON modules attempt to apply the parameters. This patch (of 2): During the calculation of &amp;#39;hot_thres&amp;#39; and &amp;#39;cold_thres&amp;#39;, either &amp;#39;sample_interval&amp;#39; or &amp;#39;aggr_interval&amp;#39; is used as the divisor, which may lead to division-by-zero errors.  Fix it by directly returning -EINVAL when such a case occurs.  Additionally, since &amp;#39;aggr_interval&amp;#39; is already required to be set no smaller than &amp;#39;sample_interval&amp;#39; in damon_set_attrs(), only the case where &amp;#39;sample_interval&amp;#39; is zero needs to be checked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39909</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2170 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2170</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen, möglicherweise um beliebigen Code auszuführen oder eine Speicherbeschädigung zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen, möglicherweise um beliebigen Code auszuführen oder eine Speicherbeschädigung zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2170</guid>
    </item>
  </channel>
</rss>
