<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 09:48:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-45029 — i2c: tegra: Do not mark ACPI devices as irq safe</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-45029</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: tegra: Do not mark ACPI devices as irq safe&lt;/p&gt;
&lt;p&gt;On ACPI machines, the tegra i2c module encounters an issue due to a
mutex being called inside a spinlock. This leads to the following bug:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:585
	...&lt;/p&gt;
&lt;p&gt;Call trace:
	__might_sleep
	__mutex_lock_common
	mutex_lock_nested
	acpi_subsys_runtime_resume
	rpm_resume
	tegra_i2c_xfer&lt;/p&gt;
&lt;p&gt;The problem arises because during __pm_runtime_resume(), the spinlock
&amp;amp;dev-&amp;gt;power.lock is acquired before rpm_resume() is called. Later,
rpm_resume() invokes acpi_subsys_runtime_resume(), which relies on
mutexes, triggering the error.&lt;/p&gt;
&lt;p&gt;To address this issue, devices on ACPI are now marked as not IRQ-safe,
considering the dependency of acpi_subsys_runtime_resume() on mutexes.&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: tegra: Do not mark ACPI devices as irq safe&lt;/p&gt;
&lt;p&gt;On ACPI machines, the tegra i2c module encounters an issue due to a
mutex being called inside a spinlock. This leads to the following bug:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:585
	...&lt;/p&gt;
&lt;p&gt;Call trace:
	__might_sleep
	__mutex_lock_common
	mutex_lock_nested
	acpi_subsys_runtime_resume
	rpm_resume
	tegra_i2c_xfer&lt;/p&gt;
&lt;p&gt;The problem arises because during __pm_runtime_resume(), the spinlock
&amp;amp;dev-&amp;gt;power.lock is acquired before rpm_resume() is called. Later,
rpm_resume() invokes acpi_subsys_runtime_resume(), which relies on
mutexes, triggering the error.&lt;/p&gt;
&lt;p&gt;To address this issue, devices on ACPI are now marked as not IRQ-safe,
considering the dependency of acpi_subsys_runtime_resume() on mutexes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-45029</guid>
    </item>
  </channel>
</rss>
