CVE-2024-45029i2c: tegra: Do not mark ACPI devices as irq safe
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 21 days later
· 21 days later
Published
- 20 months later
· 20 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < a89aef1e6cc43fa019a58080ed05c839e6c77876
- affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 6861faf4232e4b78878f2de1ed3ee324ddae2287
- affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 2853e1376d8161b04c9ff18ba82b43f08a049905
- affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 14d069d92951a3e150c0a81f2ca3b93e54da913b
- affected 5.17
- unaffected < 5.17
- unaffected 6.1.107 – ≤ 6.1.*
- unaffected 6.6.48 – ≤ 6.6.*
- unaffected 6.10.7 – ≤ 6.10.*
- unaffected 6.11 – ≤ *
References
References5
- https://git.kernel.org/stable/c/a89aef1e6cc43fa019a58080ed05c839e6c77876 (opens in a new tab)
- https://git.kernel.org/stable/c/6861faf4232e4b78878f2de1ed3ee324ddae2287 (opens in a new tab)
- https://git.kernel.org/stable/c/2853e1376d8161b04c9ff18ba82b43f08a049905 (opens in a new tab)
- https://git.kernel.org/stable/c/14d069d92951a3e150c0a81f2ca3b93e54da913b (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-41364 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-45029)Record last updated .