<?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>Thu, 15 Oct 2026 06:17:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39937 — net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-39937</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;net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer&lt;/p&gt;
&lt;p&gt;Since commit 7d5e9737efda (&amp;#34;net: rfkill: gpio: get the name and type from
device property&amp;#34;) rfkill_find_type() gets called with the possibly
uninitialized &amp;#34;const char *type_name;&amp;#34; local variable.&lt;/p&gt;
&lt;p&gt;On x86 systems when rfkill-gpio binds to a &amp;#34;BCM4752&amp;#34; or &amp;#34;LNV4752&amp;#34;
acpi_device, the rfkill-&amp;gt;type is set based on the ACPI acpi_device_id:&lt;/p&gt;
&lt;p&gt;rfkill-&amp;gt;type = (unsigned)id-&amp;gt;driver_data;&lt;/p&gt;
&lt;p&gt;and there is no &amp;#34;type&amp;#34; property so device_property_read_string() will fail
and leave type_name uninitialized, leading to a potential crash.&lt;/p&gt;
&lt;p&gt;rfkill_find_type() does accept a NULL pointer, fix the potential crash
by initializing type_name to NULL.&lt;/p&gt;
&lt;p&gt;Note likely sofar this has not been caught because:&lt;/p&gt;
&lt;p&gt;1. Not many x86 machines actually have a &amp;#34;BCM4752&amp;#34;/&amp;#34;LNV4752&amp;#34; acpi_device
2. The stack happened to contain NULL where type_name is stored&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;net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer&lt;/p&gt;
&lt;p&gt;Since commit 7d5e9737efda (&amp;#34;net: rfkill: gpio: get the name and type from
device property&amp;#34;) rfkill_find_type() gets called with the possibly
uninitialized &amp;#34;const char *type_name;&amp;#34; local variable.&lt;/p&gt;
&lt;p&gt;On x86 systems when rfkill-gpio binds to a &amp;#34;BCM4752&amp;#34; or &amp;#34;LNV4752&amp;#34;
acpi_device, the rfkill-&amp;gt;type is set based on the ACPI acpi_device_id:&lt;/p&gt;
&lt;p&gt;rfkill-&amp;gt;type = (unsigned)id-&amp;gt;driver_data;&lt;/p&gt;
&lt;p&gt;and there is no &amp;#34;type&amp;#34; property so device_property_read_string() will fail
and leave type_name uninitialized, leading to a potential crash.&lt;/p&gt;
&lt;p&gt;rfkill_find_type() does accept a NULL pointer, fix the potential crash
by initializing type_name to NULL.&lt;/p&gt;
&lt;p&gt;Note likely sofar this has not been caught because:&lt;/p&gt;
&lt;p&gt;1. Not many x86 machines actually have a &amp;#34;BCM4752&amp;#34;/&amp;#34;LNV4752&amp;#34; acpi_device
2. The stack happened to contain NULL where type_name is stored&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-39937</guid>
    </item>
    <item>
      <title>USN-8033-1 — linux, linux-aws, linux-gcp, linux-gke, linux-gkeop, linux-hwe-5.15, linux-ibm, linux-ibm-5.15, linux-lowlatency, linux…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8033-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-lowlatency&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:
  - Nios II architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bus devices;
  - Hardware random number generator core;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HW tracing;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PWM drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Userspace I/O drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - BTRFS file system;
  - File systems infrastructure;
  - Ext4 file system;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - padata parallel execution mechanism;
  - IP tunnels definitions;
  - Network sockets;
  - XFRM subsystem;
  - Control group (cgroup);
  - Padata parallel execution mechanism;
  - PID allocator;
  - Tracing infrastructure;
  - Memory management;
  - 9…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-lowlatency&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:
  - Nios II architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bus devices;
  - Hardware random number generator core;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HW tracing;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PWM drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Userspace I/O drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - BTRFS file system;
  - File systems infrastructure;
  - Ext4 file system;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - padata parallel execution mechanism;
  - IP tunnels definitions;
  - Network sockets;
  - XFRM subsystem;
  - Control group (cgroup);
  - Padata parallel execution mechanism;
  - PID allocator;
  - Tracing infrastructure;
  - Memory management;
  - 9…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8033-1</guid>
    </item>
  </channel>
</rss>
