<?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, 16 Oct 2026 00:33:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38585 — staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38585</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int()&lt;/p&gt;
&lt;p&gt;When gmin_get_config_var() calls efi.get_variable() and the EFI variable
is larger than the expected buffer size, two behaviors combine to create
a stack buffer overflow:&lt;/p&gt;
&lt;p&gt;1. gmin_get_config_var() does not return the proper error code when
   efi.get_variable() fails. It returns the stale &amp;#39;ret&amp;#39; value from
   earlier operations instead of indicating the EFI failure.&lt;/p&gt;
&lt;p&gt;2. When efi.get_variable() returns EFI_BUFFER_TOO_SMALL, it updates
   *out_len to the required buffer size but writes no data to the output
   buffer. However, due to bug #1, gmin_get_var_int() believes the call
   succeeded.&lt;/p&gt;
&lt;p&gt;The caller gmin_get_var_int() then performs:
- Allocates val[CFG_VAR_NAME_MAX + 1] (65 bytes) on stack
- Calls gmin_get_config_var(dev, is_gmin, var, val, &amp;amp;len) with len=64
- If EFI variable is &amp;gt;64 bytes, efi.get_variable() sets len=required_size
- Due to bug #1, thinks call succeeded with len=required_size
- Executes val[len] = 0, writing past end of 65-byte stack buffer&lt;/p&gt;
&lt;p&gt;This creates a stack buffer overflow when EFI variables are larger than
64 bytes. Since EFI variables can be controlled by firmware or system
configuration, this could potentially be exploited for code execution.&lt;/p&gt;
&lt;p&gt;Fix the bug by returning proper error codes from gmin_get_config_var()
based on EFI status instead of stale &amp;#39;ret&amp;#39; value.&lt;/p&gt;
&lt;p&gt;The gmin_get_var_int() function is called durin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int()&lt;/p&gt;
&lt;p&gt;When gmin_get_config_var() calls efi.get_variable() and the EFI variable
is larger than the expected buffer size, two behaviors combine to create
a stack buffer overflow:&lt;/p&gt;
&lt;p&gt;1. gmin_get_config_var() does not return the proper error code when
   efi.get_variable() fails. It returns the stale &amp;#39;ret&amp;#39; value from
   earlier operations instead of indicating the EFI failure.&lt;/p&gt;
&lt;p&gt;2. When efi.get_variable() returns EFI_BUFFER_TOO_SMALL, it updates
   *out_len to the required buffer size but writes no data to the output
   buffer. However, due to bug #1, gmin_get_var_int() believes the call
   succeeded.&lt;/p&gt;
&lt;p&gt;The caller gmin_get_var_int() then performs:
- Allocates val[CFG_VAR_NAME_MAX + 1] (65 bytes) on stack
- Calls gmin_get_config_var(dev, is_gmin, var, val, &amp;amp;len) with len=64
- If EFI variable is &amp;gt;64 bytes, efi.get_variable() sets len=required_size
- Due to bug #1, thinks call succeeded with len=required_size
- Executes val[len] = 0, writing past end of 65-byte stack buffer&lt;/p&gt;
&lt;p&gt;This creates a stack buffer overflow when EFI variables are larger than
64 bytes. Since EFI variables can be controlled by firmware or system
configuration, this could potentially be exploited for code execution.&lt;/p&gt;
&lt;p&gt;Fix the bug by returning proper error codes from gmin_get_config_var()
based on EFI status instead of stale &amp;#39;ret&amp;#39; value.&lt;/p&gt;
&lt;p&gt;The gmin_get_var_int() function is called durin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38585</guid>
    </item>
    <item>
      <title>USN-7879-1 — linux, linux-aws, linux-gcp, linux-hwe-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7879-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7879-1</guid>
    </item>
  </channel>
</rss>
