<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T23:55:35.806779+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-03934</id>
    <title>bdu:2026-03934</title>
    <updated>2026-10-12T23:55:35.816006+00:00</updated>
    <content>bdu:2026-03934</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-03934"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-53193</id>
    <title>BELL-CVE-2024-53193</title>
    <updated>2026-10-12T23:55:35.816037+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2024-53193"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</id>
    <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-10-12T23:55:35.816064+00:00</updated>
    <content>certfr-2025-avi-0152</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-346442</id>
    <title>EUVD-2026-346442</title>
    <updated>2026-10-12T23:55:35.816080+00:00</updated>
    <content>EUVD-2026-346442</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-346442"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53193</id>
    <title>fkie_cve-2024-53193</title>
    <updated>2026-10-12T23:55:35.816091+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>clk: clk-loongson2: Fix memory corruption bug in struct loongson2_clk_provider</p>
<p>Some heap space is allocated for the flexible structure `struct
clk_hw_onecell_data` and its flexible-array member `hws` through
the composite structure `struct loongson2_clk_provider` in function
`loongson2_clk_probe()`, as shown below:</p>
<p>289         struct loongson2_clk_provider *clp;
	...
296         for (p = data; p-&gt;name; p++)
297                 clks_num++;
298
299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),
300                            GFP_KERNEL);</p>
<p>Then some data is written into the flexible array:</p>
<p>350                 clp-&gt;clk_data.hws[p-&gt;id] = hw;</p>
<p>This corrupts `clk_lock`, which is the spinlock variable immediately
following the `clk_data` member in `struct loongson2_clk_provider`:</p>
<p>struct loongson2_clk_provider {
	void __iomem *base;
	struct device *dev;
	struct clk_hw_onecell_data clk_data;
	spinlock_t clk_lock;	/* protect access to DIV registers */
};</p>
<p>The problem is that the flexible structure is currently placed in the
middle of `struct loongson2_clk_provider` instead of at the end.</p>
<p>Fix this by moving `struct clk_hw_onecell_data clk_data;` to the end of
`struct loongson2_clk_provider`. Also, add a code comment to help
prevent this from happening again in case new members are added to the
structure in the future.</p>
<p>This change also fixes the following -Wflex-array-member-not-at-end
w…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-53193"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vr6j-92c6-9p78</id>
    <title>GHSA-vr6j-92c6-9p78</title>
    <updated>2026-10-12T23:55:35.816133+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>clk: clk-loongson2: Fix memory corruption bug in struct loongson2_clk_provider</p>
<p>Some heap space is allocated for the flexible structure `struct
clk_hw_onecell_data` and its flexible-array member `hws` through
the composite structure `struct loongson2_clk_provider` in function
`loongson2_clk_probe()`, as shown below:</p>
<p>289         struct loongson2_clk_provider *clp;
	...
296         for (p = data; p-&gt;name; p++)
297                 clks_num++;
298
299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),
300                            GFP_KERNEL);</p>
<p>Then some data is written into the flexible array:</p>
<p>350                 clp-&gt;clk_data.hws[p-&gt;id] = hw;</p>
<p>This corrupts `clk_lock`, which is the spinlock variable immediately
following the `clk_data` member in `struct loongson2_clk_provider`:</p>
<p>struct loongson2_clk_provider {
	void __iomem *base;
	struct device *dev;
	struct clk_hw_onecell_data clk_data;
	spinlock_t clk_lock;	/* protect access to DIV registers */
};</p>
<p>The problem is that the flexible structure is currently placed in the
middle of `struct loongson2_clk_provider` instead of at the end.</p>
<p>Fix this by moving `struct clk_hw_onecell_data clk_data;` to the end of
`struct loongson2_clk_provider`. Also, add a code comment to help
prevent this from happening again in case new members are added to the
structure in the future.</p>
<p>This change also fixes the following -Wflex-array-member-not-at-end
w…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vr6j-92c6-9p78"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53193</id>
    <title>UBUNTU-CVE-2024-53193</title>
    <updated>2026-10-12T23:55:35.816166+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 70 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: clk: clk-loongson2: Fix memory corruption bug in struct loongson2_clk_provider Some heap space is allocated for the flexible structure `struct clk_hw_onecell_data` and its flexible-array member `hws` through the composite structure `struct loongson2_clk_provider` in function `loongson2_clk_probe()`, as shown below: 289         struct loongson2_clk_provider *clp; 	... 296         for (p = data; p-&gt;name; p++) 297                 clks_num++; 298 299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num), 300                            GFP_KERNEL); Then some data is written into the flexible array: 350                 clp-&gt;clk_data.hws[p-&gt;id] = hw; This corrupts `clk_lock`, which is the spinlock variable immediately following the `clk_data` member in `struct loongson2_clk_provider`: struct loongson2_clk_provider { 	void __iomem *base; 	struct device *dev; 	struct clk_hw_onecell_data clk_data; 	spinlock_t clk_lock;	/* protect access to DIV registers */ }; The problem is that the flexible structure is currently placed in the middle of `struct loongson2_clk_provider` instead of at the end. Fix this by moving `struct clk_hw_onecell_data clk_data;` to the end of `struct loongson2_clk_provider`. Also, add a code comment to help prevent this from happening again in case new members are added to the structure in the future. This change also fixes the following -Wflex-array-member-not-at-end warning: dr…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53193"/>
  </entry>
</feed>
