🛡️ CVE-2024-57889 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking

In the Linux kernel, the following vulnerability has been resolved:

pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking

If a device uses MCP23xxx IO expander to receive IRQs, the following

bug can happen:

BUG: sleeping function called from invalid context

at kernel/locking/mutex.c:283

in_atomic(): 1, irqs_disabled(): 1, non_block: 0, ...

preempt_count: 1, expected: 0

...

Call Trace:

...

__might_resched+0x104/0x10e

__might_sleep+0x3e/0x62

mutex_lock+0x20/0x4c

regmap_lock_mutex+0x10/0x18

regmap_update_bits_base+0x2c/0x66

mcp23s08_irq_set_type+0x1ae/0x1d6

__irq_set_trigger+0x56/0x172

__setup_irq+0x1e6/0x646

request_threaded_irq+0xb6/0x160

...

We observed the problem while experimenting with a touchscreen driver which

used MCP23017 IO expander (I2C).

The regmap in the pinctrl-mcp23s08 driver uses a mutex for protection from

concurrent accesses, which is the default for regmaps without .fast_io,

.disable_locking, etc.

mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter

locks the mutex.

However, __setup_irq() locks desc->lock spinlock before calling these

functions. As a result, the system tries to lock the mutex whole holding

the spinlock.

It seems, the internal regmap locks are not needed in this driver at all.

mcp->lock seems to protect the regmap from concurrent accesses already,

except, probably, in mcp_pinconf_get/set.

mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under

chip_bus_lock(), which calls mcp23s08_irq_bus_lock(). The latter takes

mcp->lock and enables regmap caching, so that the potentially slow I2C

accesses are deferred until chip_bus_unlock().

The accesses to the regmap from mcp23s08_probe_one() do not need additional

locking.

In all remaining places where the regmap is accessed, except

mcp_pinconf_get/set(), the driver already takes mcp->lock.

This patch adds locking in mcp_pinconf_get/set() and disables internal

locking in the regmap config. Among other things, it fixes the sleeping

in atomic context described above.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-57889 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.12.9)
  • linux-kernel

Timeline and source

Published on 15 January 2025 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
lists.debian.org (Web)
lists.debian.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-57889 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-01-15
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.12.9
linux-kernel

References

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-57889 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.