CVE-2024-57889: pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking

Published Jan 15, 2025
·
Updated

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 inatomic(): 1, irqsdisabled(): 1, nonblock: 0, ... preemptcount: 1, expected: 0 ... Call Trace: ... mightresched+0x104/0x10e mightsleep+0x3e/0x62 mutexlock+0x20/0x4c regmaplockmutex+0x10/0x18 regmapupdatebitsbase+0x2c/0x66 mcp23s08irqsettype+0x1ae/0x1d6 irqsettrigger+0x56/0x172 setupirq+0x1e6/0x646 requestthreadedirq+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 .fastio, .disablelocking, etc.

mcp23s08irqsettype() calls regmapupdatebitsbase(), and the latter locks the mutex.

However, setupirq() 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 mcppinconfget/set.

mcp23s08irqsettype() and mcp23s08irqmask/unmask() are called under chipbuslock(), which calls mcp23s08irqbuslock(). The latter takes mcp->lock and enables regmap caching, so that the potentially slow I2C accesses are deferred until chipbusunlock().

The accesses to the regmap from mcp23s08probeone() do not need additional locking.

In all remaining places where the regmap is accessed, except mcppinconfget/set(), the driver already takes mcp->lock.

This patch adds locking in mcppinconfget/set() and disables internal locking in the regmap config. Among other things, it fixes the sleeping in atomic context described above.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

15 affected componentsFixes available
Linux Linux kernel
Linux pinctrl-mcp23s08
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Linux Linux kernel>=4.13<5.4.289
Linux Linux kernel>=5.5<5.10.233
Linux Linux kernel>=5.11<5.15.176
Linux Linux kernel>=5.16<6.1.124
Linux Linux kernel>=6.2<6.6.70
Linux Linux kernel>=6.7<6.12.9
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
Linux Linux kernel=6.13-rc4
Linux Linux kernel=6.13-rc5

Event History

Jan 15, 2025
CVE Published
via MITRE·01:05 PM
Data Sourced
via MITRE·01:05 PM
Description
Data Sourced
via NVD·01:15 PM
Description
Data Sourced
via NVD·01:15 PM
RemedySeverityWeaknessAffected Software
Mar 27, 2025
Data Sourced
via Launchpad·06:48 PM
Description
May 2, 2025
Data Sourced
via Ubuntu·06:56 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-57889?

CVE-2024-57889 has been classified as a medium severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2024-57889?

To fix CVE-2024-57889, update to the latest version of the Linux kernel that includes the patch for this vulnerability.

3

What systems are affected by CVE-2024-57889?

CVE-2024-57889 affects devices utilizing the MCP23xxx IO expander in the Linux kernel.

4

What are the implications of CVE-2024-57889?

CVE-2024-57889 can lead to the potential crashing of the system due to sleeping in atomic context.

5

When was CVE-2024-57889 disclosed?

CVE-2024-57889 was disclosed in the Linux kernel's updates including fixes for the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203