<?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, 08 Oct 2026 13:43:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50002 — static_call: Handle module init failure correctly in static_call_del_module()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-50002</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;static_call: Handle module init failure correctly in static_call_del_module()&lt;/p&gt;
&lt;p&gt;Module insertion invokes static_call_add_module() to initialize the static
calls in a module. static_call_add_module() invokes __static_call_init(),
which allocates a struct static_call_mod to either encapsulate the built-in
static call sites of the associated key into it so further modules can be
added or to append the module to the module chain.&lt;/p&gt;
&lt;p&gt;If that allocation fails the function returns with an error code and the
module core invokes static_call_del_module() to clean up eventually added
static_call_mod entries.&lt;/p&gt;
&lt;p&gt;This works correctly, when all keys used by the module were converted over
to a module chain before the failure. If not then static_call_del_module()
causes a #GP as it blindly assumes that key::mods points to a valid struct
static_call_mod.&lt;/p&gt;
&lt;p&gt;The problem is that key::mods is not a individual struct member of struct
static_call_key, it&amp;#39;s part of a union to save space:&lt;/p&gt;
&lt;p&gt;union {
                /* bit 0: 0 = mods, 1 = sites */
                unsigned long type;
                struct static_call_mod *mods;
                struct static_call_site *sites;
	};&lt;/p&gt;
&lt;p&gt;key::sites is a pointer to the list of built-in usage sites of the static
call. The type of the pointer is differentiated by bit 0. A mods pointer
has the bit clear, the sites pointer has the bit set.&lt;/p&gt;
&lt;p&gt;As static_call_del_module() blidly assumes that the po…&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;static_call: Handle module init failure correctly in static_call_del_module()&lt;/p&gt;
&lt;p&gt;Module insertion invokes static_call_add_module() to initialize the static
calls in a module. static_call_add_module() invokes __static_call_init(),
which allocates a struct static_call_mod to either encapsulate the built-in
static call sites of the associated key into it so further modules can be
added or to append the module to the module chain.&lt;/p&gt;
&lt;p&gt;If that allocation fails the function returns with an error code and the
module core invokes static_call_del_module() to clean up eventually added
static_call_mod entries.&lt;/p&gt;
&lt;p&gt;This works correctly, when all keys used by the module were converted over
to a module chain before the failure. If not then static_call_del_module()
causes a #GP as it blindly assumes that key::mods points to a valid struct
static_call_mod.&lt;/p&gt;
&lt;p&gt;The problem is that key::mods is not a individual struct member of struct
static_call_key, it&amp;#39;s part of a union to save space:&lt;/p&gt;
&lt;p&gt;union {
                /* bit 0: 0 = mods, 1 = sites */
                unsigned long type;
                struct static_call_mod *mods;
                struct static_call_site *sites;
	};&lt;/p&gt;
&lt;p&gt;key::sites is a pointer to the list of built-in usage sites of the static
call. The type of the pointer is differentiated by bit 0. A mods pointer
has the bit clear, the sites pointer has the bit set.&lt;/p&gt;
&lt;p&gt;As static_call_del_module() blidly assumes that the po…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-50002</guid>
    </item>
    <item>
      <title>USN-7166-1 — linux, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-kvm, linux-lowlatency, linux…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, 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-kvm and 4 more&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:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, 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-kvm and 4 more&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:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7166-1</guid>
    </item>
  </channel>
</rss>
