Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 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

CVSS scores of CVE-2024-45029, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS: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
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < a89aef1e6cc43fa019a58080ed05c839e6c77876
    • affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 6861faf4232e4b78878f2de1ed3ee324ddae2287
    • affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 2853e1376d8161b04c9ff18ba82b43f08a049905
    • affected bd2fdedbf2bac27f4a2ac16b84ab9b9e5f67006c – < 14d069d92951a3e150c0a81f2ca3b93e54da913b
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-45029 badge
[![CVE-2024-45029](https://cveledger.app/badge/CVE-2024-45029.svg)](https://cveledger.app/cve/CVE-2024-45029)

Record last updated .