<?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 09:27:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49985 — i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-49985</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;i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume&lt;/p&gt;
&lt;p&gt;In case there is any sort of clock controller attached to this I2C bus
controller, for example Versaclock or even an AIC32x4 I2C codec, then
an I2C transfer triggered from the clock controller clk_ops .prepare
callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.&lt;/p&gt;
&lt;p&gt;This is because the clock controller first grabs the prepare_lock mutex
and then performs the prepare operation, including its I2C access. The
I2C access resumes this I2C bus controller via .runtime_resume callback,
which calls clk_prepare_enable(), which attempts to grab the prepare_lock
mutex again and deadlocks.&lt;/p&gt;
&lt;p&gt;Since the clock are already prepared since probe() and unprepared in
remove(), use simple clk_enable()/clk_disable() calls to enable and
disable the clock on runtime suspend and resume, to avoid hitting the
prepare_lock mutex.&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;i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume&lt;/p&gt;
&lt;p&gt;In case there is any sort of clock controller attached to this I2C bus
controller, for example Versaclock or even an AIC32x4 I2C codec, then
an I2C transfer triggered from the clock controller clk_ops .prepare
callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.&lt;/p&gt;
&lt;p&gt;This is because the clock controller first grabs the prepare_lock mutex
and then performs the prepare operation, including its I2C access. The
I2C access resumes this I2C bus controller via .runtime_resume callback,
which calls clk_prepare_enable(), which attempts to grab the prepare_lock
mutex again and deadlocks.&lt;/p&gt;
&lt;p&gt;Since the clock are already prepared since probe() and unprepared in
remove(), use simple clk_enable()/clk_disable() calls to enable and
disable the clock on runtime suspend and resume, to avoid hitting the
prepare_lock mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-49985</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>
