<?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 02:46:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-16199</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-16199</link>
      <description>bdu:2025-16199</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-16199</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-49976</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-49976</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-49976</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1102 — 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-2024-avi-1102</link>
      <description>certfr-2024-avi-1102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-1102</guid>
    </item>
    <item>
      <title>EUVD-2026-320707</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320707</link>
      <description>EUVD-2026-320707</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320707</guid>
    </item>
    <item>
      <title>fkie_cve-2024-49976</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-49976</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&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/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-49976</guid>
    </item>
    <item>
      <title>GHSA-8j66-8f4j-h263</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8j66-8f4j-h263</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&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/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8j66-8f4j-h263</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-49976 — tracing/timerlat: Drop interface_lock in stop_kthread()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-49976</link>
      <description>msrc_CVE-2024-49976</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-49976</guid>
    </item>
    <item>
      <title>OESA-2024-2325 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2325</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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2325</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:4314-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:4314-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-2024:4314-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-49976</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49976</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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Drop interface_lock in stop_kthread() stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is introduced: T1                            | T2 [BP]               | T3 [AP] osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()                               |   _cpu_down()         |   osnoise_cpu_die()   mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()                               |     cpus_write_lock() | mutex_lock(&amp;amp;interface_lock)   cpus_read_lock()            |     cpuhp_kick_ap()   | As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of the osn_var, use xchg() instead to fix this issue. Also use for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take cpu_read_lock() again.&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 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Drop interface_lock in stop_kthread() stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is introduced: T1                            | T2 [BP]               | T3 [AP] osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()                               |   _cpu_down()         |   osnoise_cpu_die()   mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()                               |     cpus_write_lock() | mutex_lock(&amp;amp;interface_lock)   cpus_read_lock()            |     cpuhp_kick_ap()   | As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of the osn_var, use xchg() instead to fix this issue. Also use for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take cpu_read_lock() again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49976</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</guid>
    </item>
  </channel>
</rss>
