pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (Linux Linux)
En bref
- Source
- NVD
- EPSS
- EPSS 0.17 % · centile 6 ()
- État
- PUBLISHED
- Publiée
- Mise à jour
- Attribuée par
- Linux
- Statut NVD
- Modified
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.
Faiblesses (CWE)
- CWE-667 — Improper Locking
Références
- https://git.kernel.org/stable/c/788d9e9a41b81893d6bb8faa05f045c975278318
- https://git.kernel.org/stable/c/c55d186376a87b468c9ee30f2195e0f3857f61a0
- https://git.kernel.org/stable/c/9372e160d8211a7e17f2abff8370794f182df785
- https://git.kernel.org/stable/c/0310cbad163a908d09d99c26827859365cd71fcb
- https://git.kernel.org/stable/c/8c6fd5803b988a5e78c9b9e42c70a936d7cfc6ec
- https://git.kernel.org/stable/c/830f838589522404cd7c2f0f540602f25034af61
- https://git.kernel.org/stable/c/a37eecb705f33726f1fb7cd2a67e514a15dfe693
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Scores
| Version | Score | Vecteur | Évalué par |
|---|---|---|---|
| CVSS 3.1 | MEDIUM 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | NVD · nvd@nist.gov (Primary) |
Références européennes
- ENISA EUVD · EUVD-2024-53792
- GCVE · GCVE-0-2024-57889
Avis du CERT-FR
- CERTFR-2025-AVI-0366 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0349 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0308 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0276 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0254 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0234 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0212 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0184 — Multiples vulnérabilités dans le noyau Linux de Debian LTS · cert.ssi.gouv.fr
- CERTFR-2025-AVI-0183 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
Configurations affectées (CPE NVD)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 4.13 < 5.4.289cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 5.5 < 5.10.233cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 5.11 < 5.15.176cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 5.16 < 6.1.124cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 6.2 < 6.6.70cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 6.7 < 6.12.9cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
Produits affectés
| Produit | Versions |
|---|---|
| Linux · Linux | affected 8f38910ba4f662222157ce07a0d5becc4328c46a < 788d9e9a41b81893d6bb8faa05f045c975278318 ; affected 8f38910ba4f662222157ce07a0d5becc4328c46a < c55d186376a87b468c9ee30f2195e0f3857f61a0 ; affected 8f38910ba4f662222157ce07a0d5becc4328c46a < 9372e160d8211a7e17f2abff8370794f182df785 ; affected 8f38910ba4f662222157ce07a0d5becc4328c46a < 0310cbad163a908d09d99c26827859365cd71fcb ; affected 8f38910ba4f662222157ce07a0d5becc4328c46a < 8c6fd5803b988a5e78c9b9e42c70a936d7cfc6ec ; affected 8f38910ba4f662222157ce07a0d5becc4328c46a < 830f838589522404cd7c2f0f540602f25034af61 |
| Linux · Linux | affected 4.13 ; unaffected 0 < 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.* |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| CERT-FR (ANSSI) | Licence Ouverte / Etalab 2.0 |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |