<?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 16:13:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-09851</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-09851</link>
      <description>bdu:2024-09851</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-09851</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-27074</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-27074</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-27074</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381</link>
      <description>certfr-2024-avi-0381</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381</guid>
    </item>
    <item>
      <title>EUVD-2026-312719</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312719</link>
      <description>EUVD-2026-312719</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312719</guid>
    </item>
    <item>
      <title>fkie_cve-2024-27074</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-27074</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: go7007: fix a memleak in go7007_load_encoder&lt;/p&gt;
&lt;p&gt;In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&lt;/p&gt;
&lt;p&gt;saa7134_go7007_init
  |-&amp;gt; go7007_boot_encoder
        |-&amp;gt; go7007_load_encoder
  |-&amp;gt; kfree(go)&lt;/p&gt;
&lt;p&gt;go is freed and thus bounce is leaked.&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: go7007: fix a memleak in go7007_load_encoder&lt;/p&gt;
&lt;p&gt;In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&lt;/p&gt;
&lt;p&gt;saa7134_go7007_init
  |-&amp;gt; go7007_boot_encoder
        |-&amp;gt; go7007_load_encoder
  |-&amp;gt; kfree(go)&lt;/p&gt;
&lt;p&gt;go is freed and thus bounce is leaked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-27074</guid>
    </item>
    <item>
      <title>GHSA-m4vr-jmc8-6xrj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m4vr-jmc8-6xrj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: go7007: fix a memleak in go7007_load_encoder&lt;/p&gt;
&lt;p&gt;In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&lt;/p&gt;
&lt;p&gt;saa7134_go7007_init
  |-&amp;gt; go7007_boot_encoder
        |-&amp;gt; go7007_load_encoder
  |-&amp;gt; kfree(go)&lt;/p&gt;
&lt;p&gt;go is freed and thus bounce is leaked.&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: go7007: fix a memleak in go7007_load_encoder&lt;/p&gt;
&lt;p&gt;In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&lt;/p&gt;
&lt;p&gt;saa7134_go7007_init
  |-&amp;gt; go7007_boot_encoder
        |-&amp;gt; go7007_load_encoder
  |-&amp;gt; kfree(go)&lt;/p&gt;
&lt;p&gt;go is freed and thus bounce is leaked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m4vr-jmc8-6xrj</guid>
    </item>
    <item>
      <title>gsd-2024-27074</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-27074</link>
      <description>gsd-2024-27074</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-27074</guid>
    </item>
    <item>
      <title>ICSA-23-348-10 — Siemens SIMATIC S7-1500</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-23-348-10</link>
      <description>&lt;p&gt;expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue.  NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE. shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename. In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start o…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue.  NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE. shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename. In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-23-348-10</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-27074 — media: go7007: fix a memleak in go7007_load_encoder</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-27074</link>
      <description>msrc_CVE-2024-27074</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-27074</guid>
    </item>
    <item>
      <title>OESA-2024-1617 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1617</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: 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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: 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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1617</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1643-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1643-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:1643-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-27074</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27074</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 171 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: go7007: fix a memleak in go7007_load_encoder In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without a deallocation thereafter. After the following call chain: saa7134_go7007_init   |-&amp;gt; go7007_boot_encoder         |-&amp;gt; go7007_load_encoder   |-&amp;gt; kfree(go) go is freed and thus bounce is leaked.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 171 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: go7007: fix a memleak in go7007_load_encoder In go7007_load_encoder, bounce(i.e. go-&amp;gt;boot_fw), is allocated without a deallocation thereafter. After the following call chain: saa7134_go7007_init   |-&amp;gt; go7007_boot_encoder         |-&amp;gt; go7007_load_encoder   |-&amp;gt; kfree(go) go is freed and thus bounce is leaked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27074</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1008 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1008</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder sonstige Auswirkungen zu verursachen.&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 sonstige Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1008</guid>
    </item>
  </channel>
</rss>
