CVE-2024-45029: i2c: tegra: Do not mark ACPI devices as irq safe

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-09-11 · updated 2026-06-17
Weakness: CWE-667

Description

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: Do not mark ACPI devices as irq safe 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: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:585 ... Call trace: __might_sleep __mutex_lock_common mutex_lock_nested acpi_subsys_runtime_resume rpm_resume tegra_i2c_xfer The problem arises because during __pm_runtime_resume(), the spinlock &dev->power.lock is acquired before rpm_resume() is called. Later, rpm_resume() invokes acpi_subsys_runtime_resume(), which relies on mutexes, triggering the error. To address this issue, devices on ACPI are now marked as not IRQ-safe, considering the dependency of acpi_subsys_runtime_resume() on mutexes.

Affected products

Linux kernel: from 5.17 before 6.1.107; from 6.2 before 6.6.48; from 6.7 before 6.10.7; 6.11-rc1, 6.11-rc2, 6.11-rc3 — fixed in 6.1.107, 6.10.7, 6.6.48

How to fix

Upgrade to a fixed version: Linux kernel 6.1.107, 6.10.7, 6.6.48. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-45029 or the next vulnerability affects your stack