<?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 22:27:42 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02710</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02710</link>
      <description>bdu:2026-02710</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02710</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39994</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39994</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-39994</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0899 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0899</link>
      <description>certfr-2025-avi-0899</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0899</guid>
    </item>
    <item>
      <title>EUVD-2026-347297</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347297</link>
      <description>EUVD-2026-347297</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347297</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39994</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39994</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: tuner: xc5000: Fix use-after-free in xc5000_release&lt;/p&gt;
&lt;p&gt;The original code uses cancel_delayed_work() in xc5000_release(), which
does not guarantee that the delayed work item timer_sleep has fully
completed if it was already running. This leads to use-after-free scenarios
where xc5000_release() may free the xc5000_priv while timer_sleep is still
active and attempts to dereference the xc5000_priv.&lt;/p&gt;
&lt;p&gt;A typical race condition is illustrated below:&lt;/p&gt;
&lt;p&gt;CPU 0 (release thread)                 | CPU 1 (delayed work callback)
xc5000_release()                       | xc5000_do_timer_sleep()
  cancel_delayed_work()                |
  hybrid_tuner_release_state(priv)     |
    kfree(priv)                        |
                                       |   priv = container_of() // UAF&lt;/p&gt;
&lt;p&gt;Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure
that the timer_sleep is properly canceled before the xc5000_priv memory
is deallocated.&lt;/p&gt;
&lt;p&gt;A deadlock concern was considered: xc5000_release() is called in a process
context and is not holding any locks that the timer_sleep work item might
also need. Therefore, the use of the _sync() variant is safe here.&lt;/p&gt;
&lt;p&gt;This bug was initially identified through static analysis.&lt;/p&gt;
&lt;p&gt;[hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&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;media: tuner: xc5000: Fix use-after-free in xc5000_release&lt;/p&gt;
&lt;p&gt;The original code uses cancel_delayed_work() in xc5000_release(), which
does not guarantee that the delayed work item timer_sleep has fully
completed if it was already running. This leads to use-after-free scenarios
where xc5000_release() may free the xc5000_priv while timer_sleep is still
active and attempts to dereference the xc5000_priv.&lt;/p&gt;
&lt;p&gt;A typical race condition is illustrated below:&lt;/p&gt;
&lt;p&gt;CPU 0 (release thread)                 | CPU 1 (delayed work callback)
xc5000_release()                       | xc5000_do_timer_sleep()
  cancel_delayed_work()                |
  hybrid_tuner_release_state(priv)     |
    kfree(priv)                        |
                                       |   priv = container_of() // UAF&lt;/p&gt;
&lt;p&gt;Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure
that the timer_sleep is properly canceled before the xc5000_priv memory
is deallocated.&lt;/p&gt;
&lt;p&gt;A deadlock concern was considered: xc5000_release() is called in a process
context and is not holding any locks that the timer_sleep work item might
also need. Therefore, the use of the _sync() variant is safe here.&lt;/p&gt;
&lt;p&gt;This bug was initially identified through static analysis.&lt;/p&gt;
&lt;p&gt;[hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39994</guid>
    </item>
    <item>
      <title>GHSA-ghgh-r6c5-cgx8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ghgh-r6c5-cgx8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: tuner: xc5000: Fix use-after-free in xc5000_release&lt;/p&gt;
&lt;p&gt;The original code uses cancel_delayed_work() in xc5000_release(), which
does not guarantee that the delayed work item timer_sleep has fully
completed if it was already running. This leads to use-after-free scenarios
where xc5000_release() may free the xc5000_priv while timer_sleep is still
active and attempts to dereference the xc5000_priv.&lt;/p&gt;
&lt;p&gt;A typical race condition is illustrated below:&lt;/p&gt;
&lt;p&gt;CPU 0 (release thread)                 | CPU 1 (delayed work callback)
xc5000_release()                       | xc5000_do_timer_sleep()
  cancel_delayed_work()                |
  hybrid_tuner_release_state(priv)     |
    kfree(priv)                        |
                                       |   priv = container_of() // UAF&lt;/p&gt;
&lt;p&gt;Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure
that the timer_sleep is properly canceled before the xc5000_priv memory
is deallocated.&lt;/p&gt;
&lt;p&gt;A deadlock concern was considered: xc5000_release() is called in a process
context and is not holding any locks that the timer_sleep work item might
also need. Therefore, the use of the _sync() variant is safe here.&lt;/p&gt;
&lt;p&gt;This bug was initially identified through static analysis.&lt;/p&gt;
&lt;p&gt;[hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&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;media: tuner: xc5000: Fix use-after-free in xc5000_release&lt;/p&gt;
&lt;p&gt;The original code uses cancel_delayed_work() in xc5000_release(), which
does not guarantee that the delayed work item timer_sleep has fully
completed if it was already running. This leads to use-after-free scenarios
where xc5000_release() may free the xc5000_priv while timer_sleep is still
active and attempts to dereference the xc5000_priv.&lt;/p&gt;
&lt;p&gt;A typical race condition is illustrated below:&lt;/p&gt;
&lt;p&gt;CPU 0 (release thread)                 | CPU 1 (delayed work callback)
xc5000_release()                       | xc5000_do_timer_sleep()
  cancel_delayed_work()                |
  hybrid_tuner_release_state(priv)     |
    kfree(priv)                        |
                                       |   priv = container_of() // UAF&lt;/p&gt;
&lt;p&gt;Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure
that the timer_sleep is properly canceled before the xc5000_priv memory
is deallocated.&lt;/p&gt;
&lt;p&gt;A deadlock concern was considered: xc5000_release() is called in a process
context and is not holding any locks that the timer_sleep work item might
also need. Therefore, the use of the _sync() variant is safe here.&lt;/p&gt;
&lt;p&gt;This bug was initially identified through static analysis.&lt;/p&gt;
&lt;p&gt;[hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ghgh-r6c5-cgx8</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-39994 — media: tuner: xc5000: Fix use-after-free in xc5000_release</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-39994</link>
      <description>msrc_CVE-2025-39994</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-39994</guid>
    </item>
    <item>
      <title>OESA-2025-2772 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2772</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;media: davinci: vpif: fix use-after-free on driver unbind&lt;/p&gt;
&lt;p&gt;The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.&lt;/p&gt;
&lt;p&gt;This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.&lt;/p&gt;
&lt;p&gt;Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.(CVE-2021-47653)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mmc: core: use sysfs_emit() instead of sprintf()&lt;/p&gt;
&lt;p&gt;sprintf() (still used in the MMC core for the sysfs output) is vulnerable
to the buffer overflow.  Use the new-fangled sysfs_emit() instead.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with the SVACE static
analysis tool.(CVE-2022-49267)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event&lt;/p&gt;
&lt;p&gt;We should not access skb buffer data anymore after hci_recv_frame was
called.&lt;/p&gt;
&lt;p&gt;[   39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0
[   39.634855] Read of size 1 at addr ffffff80cf28a60d by tas…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;media: davinci: vpif: fix use-after-free on driver unbind&lt;/p&gt;
&lt;p&gt;The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.&lt;/p&gt;
&lt;p&gt;This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.&lt;/p&gt;
&lt;p&gt;Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.(CVE-2021-47653)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mmc: core: use sysfs_emit() instead of sprintf()&lt;/p&gt;
&lt;p&gt;sprintf() (still used in the MMC core for the sysfs output) is vulnerable
to the buffer overflow.  Use the new-fangled sysfs_emit() instead.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with the SVACE static
analysis tool.(CVE-2022-49267)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event&lt;/p&gt;
&lt;p&gt;We should not access skb buffer data anymore after hci_recv_frame was
called.&lt;/p&gt;
&lt;p&gt;[   39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0
[   39.634855] Read of size 1 at addr ffffff80cf28a60d by tas…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2772</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:15671-1 — kernel-devel-6.17.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15671-1</link>
      <description>&lt;p&gt;kernel-devel-6.17.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.17.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:15671-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21040-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21040-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:21040-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39994</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39994</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 221 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: tuner: xc5000: Fix use-after-free in xc5000_release The original code uses cancel_delayed_work() in xc5000_release(), which does not guarantee that the delayed work item timer_sleep has fully completed if it was already running. This leads to use-after-free scenarios where xc5000_release() may free the xc5000_priv while timer_sleep is still active and attempts to dereference the xc5000_priv. A typical race condition is illustrated below: CPU 0 (release thread)                 | CPU 1 (delayed work callback) xc5000_release()                       | xc5000_do_timer_sleep()   cancel_delayed_work()                |   hybrid_tuner_release_state(priv)     |     kfree(priv)                        |                                        |   priv = container_of() // UAF Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the timer_sleep is properly canceled before the xc5000_priv memory is deallocated. A deadlock concern was considered: xc5000_release() is called in a process context and is not holding any locks that the timer_sleep work item might also need. Therefore, the use of the _sync() variant is safe here. This bug was initially identified through static analysis. [hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 221 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: tuner: xc5000: Fix use-after-free in xc5000_release The original code uses cancel_delayed_work() in xc5000_release(), which does not guarantee that the delayed work item timer_sleep has fully completed if it was already running. This leads to use-after-free scenarios where xc5000_release() may free the xc5000_priv while timer_sleep is still active and attempts to dereference the xc5000_priv. A typical race condition is illustrated below: CPU 0 (release thread)                 | CPU 1 (delayed work callback) xc5000_release()                       | xc5000_do_timer_sleep()   cancel_delayed_work()                |   hybrid_tuner_release_state(priv)     |     kfree(priv)                        |                                        |   priv = container_of() // UAF Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the timer_sleep is properly canceled before the xc5000_priv memory is deallocated. A deadlock concern was considered: xc5000_release() is called in a process context and is not holding any locks that the timer_sleep work item might also need. Therefore, the use of the _sync() variant is safe here. This bug was initially identified through static analysis. [hverkuil: fix typo in Subject: tunner -&amp;gt; tuner]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39994</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2298 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2298</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Daten zu manipulieren und andere, nicht näher spezifizierte Angriffe durchzuführen.&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, Daten zu manipulieren und andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2298</guid>
    </item>
  </channel>
</rss>
