<?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 10:08:19 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06052</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06052</link>
      <description>bdu:2024-06052</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06052</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-39291</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-39291</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-39291</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0632 — 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-0632</link>
      <description>certfr-2024-avi-0632</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632</guid>
    </item>
    <item>
      <title>cnvd-2024-31491</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-31491</link>
      <description>cnvd-2024-31491</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-31491</guid>
    </item>
    <item>
      <title>EUVD-2026-312911</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312911</link>
      <description>EUVD-2026-312911</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312911</guid>
    </item>
    <item>
      <title>fkie_cve-2024-39291</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-39291</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()&lt;/p&gt;
&lt;p&gt;The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating
about potential truncation of output when using the snprintf function.
The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too
small to accommodate the maximum possible length of the string being
written into it.&lt;/p&gt;
&lt;p&gt;The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;,
where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this
string without the %s is 16 characters. The warning message indicated
that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total
of 45 characters, which exceeds the buffer size of 30 characters.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been
reduced from 30 to 15. This ensures that the maximum possible length of
the string being written into the buffer will not exceed its size, thus
preventing potential buffer overflow and truncation issues.&lt;/p&gt;
&lt;p&gt;Fixes the below with gcc W=1:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]
  379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);
      |…&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;drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()&lt;/p&gt;
&lt;p&gt;The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating
about potential truncation of output when using the snprintf function.
The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too
small to accommodate the maximum possible length of the string being
written into it.&lt;/p&gt;
&lt;p&gt;The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;,
where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this
string without the %s is 16 characters. The warning message indicated
that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total
of 45 characters, which exceeds the buffer size of 30 characters.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been
reduced from 30 to 15. This ensures that the maximum possible length of
the string being written into the buffer will not exceed its size, thus
preventing potential buffer overflow and truncation issues.&lt;/p&gt;
&lt;p&gt;Fixes the below with gcc W=1:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]
  379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);
      |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-39291</guid>
    </item>
    <item>
      <title>GHSA-j658-fjmg-478v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j658-fjmg-478v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()&lt;/p&gt;
&lt;p&gt;The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating
about potential truncation of output when using the snprintf function.
The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too
small to accommodate the maximum possible length of the string being
written into it.&lt;/p&gt;
&lt;p&gt;The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;,
where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this
string without the %s is 16 characters. The warning message indicated
that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total
of 45 characters, which exceeds the buffer size of 30 characters.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been
reduced from 30 to 15. This ensures that the maximum possible length of
the string being written into the buffer will not exceed its size, thus
preventing potential buffer overflow and truncation issues.&lt;/p&gt;
&lt;p&gt;Fixes the below with gcc W=1:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]
  379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);
      |…&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;drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()&lt;/p&gt;
&lt;p&gt;The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating
about potential truncation of output when using the snprintf function.
The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too
small to accommodate the maximum possible length of the string being
written into it.&lt;/p&gt;
&lt;p&gt;The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;,
where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this
string without the %s is 16 characters. The warning message indicated
that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total
of 45 characters, which exceeds the buffer size of 30 characters.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been
reduced from 30 to 15. This ensures that the maximum possible length of
the string being written into the buffer will not exceed its size, thus
preventing potential buffer overflow and truncation issues.&lt;/p&gt;
&lt;p&gt;Fixes the below with gcc W=1:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’:
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]
  379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);
      |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j658-fjmg-478v</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-39291 — drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-39291</link>
      <description>msrc_CVE-2024-39291</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-39291</guid>
    </item>
    <item>
      <title>RHSA-2024:9315 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:9315</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:9315</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2571-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2571-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:2571-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-39291</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-39291</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode() The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating about potential truncation of output when using the snprintf function. The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too small to accommodate the maximum possible length of the string being written into it. The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this string without the %s is 16 characters. The warning message indicated that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total of 45 characters, which exceeds the buffer size of 30 characters. To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been reduced from 30 to 15. This ensures that the maximum possible length of the string being written into the buffer will not exceed its size, thus preventing potential buffer overflow and truncation issues. Fixes the below with gcc W=1: drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’: drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]   379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);       |                                                    ^~…&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode() The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating about potential truncation of output when using the snprintf function. The issue was due to the size of the buffer &amp;#39;ucode_prefix&amp;#39; being too small to accommodate the maximum possible length of the string being written into it. The string being written is &amp;#34;amdgpu/%s_mec.bin&amp;#34; or &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, where %s is replaced by the value of &amp;#39;chip_name&amp;#39;. The length of this string without the %s is 16 characters. The warning message indicated that &amp;#39;chip_name&amp;#39; could be up to 29 characters long, resulting in a total of 45 characters, which exceeds the buffer size of 30 characters. To resolve this issue, the size of the &amp;#39;ucode_prefix&amp;#39; buffer has been reduced from 30 to 15. This ensures that the maximum possible length of the string being written into the buffer will not exceed its size, thus preventing potential buffer overflow and truncation issues. Fixes the below with gcc W=1: drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function ‘gfx_v9_4_3_early_init’: drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: ‘%s’ directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=]   379 |         snprintf(fw_name, sizeof(fw_name), &amp;#34;amdgpu/%s_rlc.bin&amp;#34;, chip_name);       |                                                    ^~…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-39291</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1443 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1443</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1443</guid>
    </item>
  </channel>
</rss>
