Поиск уязвимостей
Количество 21
Количество 21
CVE-2024-45029
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.
CVE-2024-45029
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.
CVE-2024-45029
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.
CVE-2024-45029
i2c: tegra: Do not mark ACPI devices as irq safe
CVE-2024-45029
In the Linux kernel, the following vulnerability has been resolved: i ...
GHSA-ww57-48hq-5w83
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.
BDU:2025-01944
Уязвимость компонента i2c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
SUSE-SU-2024:3592-1
Security update for the Linux Kernel
SUSE-SU-2024:3569-1
Security update for the Linux Kernel
SUSE-SU-2024:3587-1
Security update for the Linux Kernel
SUSE-SU-2024:3553-1
Security update for the Linux Kernel
SUSE-SU-2024:3564-1
Security update for the Linux Kernel
SUSE-SU-2024:3561-1
Security update for the Linux Kernel
SUSE-SU-2024:3551-1
Security update for the Linux Kernel
ROS-20250206-01
Множественные уязвимости kernel-lt
ALT-PU-2024-11863
ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1
ALT-PU-2024-11855
ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1
ALT-PU-2024-13260
ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1
ALT-PU-2024-13121
ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1
ALT-PU-2024-13979
ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-45029 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. | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45029 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. | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45029 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. | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45029 i2c: tegra: Do not mark ACPI devices as irq safe | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45029 In the Linux kernel, the following vulnerability has been resolved: i ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
GHSA-ww57-48hq-5w83 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. | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
BDU:2025-01944 Уязвимость компонента i2c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
SUSE-SU-2024:3592-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3569-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3587-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3553-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3564-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3561-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3551-1 Security update for the Linux Kernel | около 2 лет назад | |||
ROS-20250206-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | почти 2 года назад | ||
ALT-PU-2024-11863 ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1 | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-11855 ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13260 ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13121 ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13979 ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 7.8 | около 2 лет назад |
Уязвимостей на страницу