Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-57889, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < 788d9e9a41b81893d6bb8faa05f045c975278318
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < c55d186376a87b468c9ee30f2195e0f3857f61a0
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < 9372e160d8211a7e17f2abff8370794f182df785
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < 0310cbad163a908d09d99c26827859365cd71fcb
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < 8c6fd5803b988a5e78c9b9e42c70a936d7cfc6ec
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < 830f838589522404cd7c2f0f540602f25034af61
    • affected 8f38910ba4f662222157ce07a0d5becc4328c46a – < a37eecb705f33726f1fb7cd2a67e514a15dfe693
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.4.289 – ≤ 5.4.*
    • unaffected 5.10.233 – ≤ 5.10.*
    • unaffected 5.15.176 – ≤ 5.15.*
    • unaffected 6.1.124 – ≤ 6.1.*
    • unaffected 6.6.70 – ≤ 6.6.*
    • unaffected 6.12.9 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-57889 badge
[![CVE-2024-57889](https://cveledger.app/badge/CVE-2024-57889.svg)](https://cveledger.app/cve/CVE-2024-57889)

Record last updated .