https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:08:04 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-03510 bdu:2025-03510 https://cve.radiocsirt.org/vuln/bdu:2025-03510 https://cve.radiocsirt.org/vuln/bell-cve-2024-57889 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-57889 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0183 certfr-2025-avi-0183 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0183 https://cve.radiocsirt.org/vuln/euvd-2026-313893 EUVD-2026-313893 https://cve.radiocsirt.org/vuln/euvd-2026-313893 https://cve.radiocsirt.org/vuln/fkie_cve-2024-57889 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get/set.</p> <p>mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under c…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get/set.</p> <p>mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under c…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-57889 https://cve.radiocsirt.org/vuln/ghsa-5xqg-j6jp-j9g5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get/set.</p> <p>mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under c…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get/set.</p> <p>mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under c…</p> https://cve.radiocsirt.org/vuln/ghsa-5xqg-j6jp-j9g5 https://cve.radiocsirt.org/vuln/oesa-2025-2409 <p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&amp;gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&amp;gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking</p> <p>If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:</p> <p>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 ...</p> <p>We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).</p> <p>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.</p> <p>mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.</p> <p>However, __setup_irq() locks desc-&amp;gt;lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.</p> <p>It seems, the internal regmap locks are not needed in this driver at all. mcp-&amp;gt;lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get…</p> https://cve.radiocsirt.org/vuln/oesa-2025-2409 https://cve.radiocsirt.org/vuln/suse-su-2025:0784-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:0784-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57889 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 188 more</p> <p>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-&gt;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-&gt;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_l…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 188 more</p> <p>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-&gt;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-&gt;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_l…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57889 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0105 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0105