Improper Locking Affecting reiserfs-kmp-coco package, versions <6.4.0-15061.6.coco15sp6.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.04% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-REISERFSKMPCOCO-8170479
  • published9 Oct 2024
  • disclosed8 Oct 2024

Introduced: 8 Oct 2024

CVE-2024-45029  (opens in a new tab)
CWE-667  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 reiserfs-kmp-coco to version 6.4.0-15061.6.coco15sp6.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream reiserfs-kmp-coco package and not the reiserfs-kmp-coco package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Scores

version 3.1