{"vulnerability": "CVE-2024-45029", "sightings": [{"uuid": "fbb769e2-f20f-4b67-9c88-b76f61cc9141", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45029", "type": "seen", "source": "https://t.me/cvedetector/5374", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45029 - Linux Tegra i2cacersenal/Irql Violation\", \n  \"Content\": \"CVE ID : CVE-2024-45029 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ni2c: tegra: Do not mark ACPI devices as irq safe  \n  \nOn ACPI machines, the tegra i2c module encounters an issue due to a  \nmutex being called inside a spinlock. This leads to the following bug:  \n  \n BUG: sleeping function called from invalid context at kernel/locking/mutex.c:585  \n ...  \n  \n Call trace:  \n __might_sleep  \n __mutex_lock_common  \n mutex_lock_nested  \n acpi_subsys_runtime_resume  \n rpm_resume  \n tegra_i2c_xfer  \n  \nThe problem arises because during __pm_runtime_resume(), the spinlock  \n&dev->power.lock is acquired before rpm_resume() is called. Later,  \nrpm_resume() invokes acpi_subsys_runtime_resume(), which relies on  \nmutexes, triggering the error.  \n  \nTo address this issue, devices on ACPI are now marked as not IRQ-safe,  \nconsidering the dependency of acpi_subsys_runtime_resume() on mutexes. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:28.000000Z"}]}