dbcve.org
Linux KernelOperating system · Linux

CVE-2024-45029

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-11
Fix available
A fix is available. Upgrade to 6.1.107 / 6.6.48 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-667

Shared resources are accessed without correct locking, so concurrent operations interleave into inconsistent — and sometimes exploitable — states, or deadlock the service outright. These bugs are subtle and timing-dependent. The fix is correct, consistent locking or atomic operations around every shared resource.

General guidance for the improper locking class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.17, < 6.1.107>= 6.2, < 6.6.48>= 6.7, < 6.10.7= 6.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.107 / 6.6.48 / 6.10.7 or later
Fixed in 6.1.1076.6.486.10.7
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 6.1.107+ (for 6.1.x systems), 6.6.48+ (for 6.6.x systems), 6.10.7+ (for 6.7-6.10.x systems), or 6.12+ (for 6.11+ systems)

  1. Identify the currently running kernel version using 'uname -r'
  2. Check which stable kernel series your distribution supports (e.g., 6.1.x, 6.6.x, 6.10.x, or 6.11)
  3. Update your system package repository to fetch the latest available kernel packages
  4. Upgrade the kernel package to version 6.1.107 or higher for the 6.1 series, 6.6.48 or higher for the 6.6 series, or 6.10.7 or higher for the 6.7-6.10 series
  5. Reboot the system to load the new kernel
  6. Verify the running kernel version with 'uname -r' to confirm the fix is applied
  7. If running kernel 6.11 specifically, ensure the patch from commit 14d069d92951a3e150c0a81f2ca3b93e54da913b is included in your distribution's 6.11 package, or upgrade to a newer stable release
Caveat Kernel upgrades may require matching hardware drivers and could require system reboot; ensure compatibility with existing system configurations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45029 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data